January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2697) HotRodServer startup fails when its record cannot be inserted into topology cache

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/ISPN-2697?page=com.atlassian.jira.plugin.... ] Bela Ban commented on ISPN-2697: -------------------------------- Yes, Mircea's correct: STABLE *does* indeed contain not just the highest delivered seqnos (for purging messages seen by everyone), but also the highest seen messages, so members who don't have them can request them. To wait for stability to kick in may not be the best solution though. In cases where immediate delivery is important, I suggest tagging the message as RSVP. This will effectively behave as if the message was sent with UNICAST. > HotRodServer startup fails when its record cannot be inserted into topology cache > --------------------------------------------------------------------------------- > > Key: ISPN-2697 > URL: https://issues.jboss.org/browse/ISPN-2697 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.Beta6 > Reporter: Radim Vansa > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > When the HotRodServer starts it inserts its record to __hotRodTopologyCache ({{HotRodServer.addSelfToTopologyView(...)}}). > However, this put may very easily fail - as the command is broadcasted using NAKACK2 protocol, if the message gets lost and there's no following broadcasted message, the message will be not retransmitted and the put operation times out (Replication timeout), which fails the whole HotRodServer startup, all because of one lost UDP message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2697) HotRodServer startup fails when its record cannot be inserted into topology cache

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2697?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2697: ------------------------------------- [~rvansa] That's not what I know :-) Stable doesn't only clean up stuff but also make sure that the last sent message has arrived at destination and if not force a retransmission. Good that we have [~belaban] to put some lights on this :-) > HotRodServer startup fails when its record cannot be inserted into topology cache > --------------------------------------------------------------------------------- > > Key: ISPN-2697 > URL: https://issues.jboss.org/browse/ISPN-2697 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.Beta6 > Reporter: Radim Vansa > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > When the HotRodServer starts it inserts its record to __hotRodTopologyCache ({{HotRodServer.addSelfToTopologyView(...)}}). > However, this put may very easily fail - as the command is broadcasted using NAKACK2 protocol, if the message gets lost and there's no following broadcasted message, the message will be not retransmitted and the put operation times out (Replication timeout), which fails the whole HotRodServer startup, all because of one lost UDP message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2686) Enhance Mapper API with lazy loaded value

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2686?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2686: ------------------------------------- {quote}When entry.getValue() is called, the value should be loaded from store or maybe remote node.{quote} This would be a tradeoff between loading more(potentially unnecessary) data in less queries(no query for the needed values) and less data in more queries (additional query to get the value when needed). I'd say the former is more suited for the general case: unless you don't use (almost) any values or the values are rather large/costly to fetch. > Enhance Mapper API with lazy loaded value > ----------------------------------------- > > Key: ISPN-2686 > URL: https://issues.jboss.org/browse/ISPN-2686 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.0.Beta6 > Reporter: Thomas Fromm > Assignee: Vladimir Blagojevic > > In situations where Map/Reduce is used and the value is not (always) needed at the Mapper, the value could be loaded lazy, when the map(..) interface is slightly changed: > map(Entry<KIn, VIn> entry, Collector<Entry<KIn, VIn>> collector) > When entry.getValue() is called, the value should be loaded from store or maybe remote node. > Maybe this change to Entry would be also useful for event api ISPN-1802 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2686) Enhance Mapper API with lazy loaded value

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2686?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2686: -------------------------------- Priority: Minor (was: Major) > Enhance Mapper API with lazy loaded value > ----------------------------------------- > > Key: ISPN-2686 > URL: https://issues.jboss.org/browse/ISPN-2686 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.0.Beta6 > Reporter: Thomas Fromm > Assignee: Vladimir Blagojevic > Priority: Minor > > In situations where Map/Reduce is used and the value is not (always) needed at the Mapper, the value could be loaded lazy, when the map(..) interface is slightly changed: > map(Entry<KIn, VIn> entry, Collector<Entry<KIn, VIn>> collector) > When entry.getValue() is called, the value should be loaded from store or maybe remote node. > Maybe this change to Entry would be also useful for event api ISPN-1802 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2686) Enhance Mapper API with lazy loaded value

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2686?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2686: -------------------------------- Fix Version/s: 6.0.0.Final > Enhance Mapper API with lazy loaded value > ----------------------------------------- > > Key: ISPN-2686 > URL: https://issues.jboss.org/browse/ISPN-2686 > Project: Infinispan > Issue Type: Enhancement > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.0.Beta6 > Reporter: Thomas Fromm > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 6.0.0.Final > > > In situations where Map/Reduce is used and the value is not (always) needed at the Mapper, the value could be loaded lazy, when the map(..) interface is slightly changed: > map(Entry<KIn, VIn> entry, Collector<Entry<KIn, VIn>> collector) > When entry.getValue() is called, the value should be loaded from store or maybe remote node. > Maybe this change to Entry would be also useful for event api ISPN-1802 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2697) HotRodServer startup fails when its record cannot be inserted into topology cache

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-2697?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-2697: ----------------------------------- Mircea: that's what I also thought, but this is not the UNICAST2 stabilization message - the behaviour differs. STABLE's aim is to remove old messages that are confirmed by all nodes, not to force retransmission after a period. Even the STABLE message does not contain the highest transmitted seqno, there are only highest received and highest delivered seqnos from each node. > HotRodServer startup fails when its record cannot be inserted into topology cache > --------------------------------------------------------------------------------- > > Key: ISPN-2697 > URL: https://issues.jboss.org/browse/ISPN-2697 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.Beta6 > Reporter: Radim Vansa > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > When the HotRodServer starts it inserts its record to __hotRodTopologyCache ({{HotRodServer.addSelfToTopologyView(...)}}). > However, this put may very easily fail - as the command is broadcasted using NAKACK2 protocol, if the message gets lost and there's no following broadcasted message, the message will be not retransmitted and the put operation times out (Replication timeout), which fails the whole HotRodServer startup, all because of one lost UDP message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2675) Need way to use custom create table syntax

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2675?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2675: ------------------------------------- "So I need for the 5.2 a way to provide custom create table syntax :-|" you are allowed to create the table by hand by setting "createOnStartup" to false. Isn't that good enough? > Need way to use custom create table syntax > ------------------------------------------ > > Key: ISPN-2675 > URL: https://issues.jboss.org/browse/ISPN-2675 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Affects Versions: 5.2.0.Beta6 > Reporter: Thomas Fromm > Assignee: Mircea Markus > Fix For: 5.2.0.Final > > > Currently with oracle and LOB as column type for cache value the LOB data are tried to store inline. This is expensive and a major performance issue (for me). > Details to this: http://www.idevelopment.info/data/Oracle/DBA_tips/LOBs/LOBS_2.shtml > So I need for the 5.2 a way to provide custom create table syntax :-| > Maybe a workaround could that I execute ALTER TABLE statement after cache startup, but then I need to check table attributes first if alter table statement is nessessary. Provide own create table statement is much easier. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2392) Optimize locking behaviour in non-transactional caches

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2392?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2392: ------------------------------------- [~tfromm] thanks for the feedback, this is something we need to look at. > Optimize locking behaviour in non-transactional caches > ------------------------------------------------------ > > Key: ISPN-2392 > URL: https://issues.jboss.org/browse/ISPN-2392 > Project: Infinispan > Issue Type: Enhancement > Components: Locking and Concurrency > Affects Versions: 5.2.0.Beta1 > Reporter: Thomas Fromm > Assignee: Mircea Markus > > Situation: REPL_SYNC cache, non transactional, locking isolation level NONE > Problem: when multiple threads trying to write same key on multiple nodes, the operation ends up mostly in locking timeouts > Mircea mentioned that the locking behaviour for non-tx caches could be optimized as well as for tx-caches or use the same mechanisms. > (One single lock, independed number of owners) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2632: ----------------------------------- Fix Version/s: 5.2.0.CR2 > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2326) c3p0 not part of the release

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2326?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2326: ------------------------------------- [~NadirX] might help? > c3p0 not part of the release > ---------------------------- > > Key: ISPN-2326 > URL: https://issues.jboss.org/browse/ISPN-2326 > Project: Infinispan > Issue Type: Bug > Components: Build process > Affects Versions: 5.2.0.Alpha4 > Reporter: Thomas Fromm > Assignee: Adrian Nistor > Priority: Critical > Fix For: 5.2.0.Final > > > According infinispan-5.2.0.Alpha4-all/modules/cachestores/jdbc/runtime-classpath.txt c3p0 lib should be part of the release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2013