January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2580) Do not request segments from all nodes at once

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2580?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2580: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 881070|https://bugzilla.redhat.com/show_bug.cgi?id=881070] from ASSIGNED to MODIFIED > Do not request segments from all nodes at once > ---------------------------------------------- > > Key: ISPN-2580 > URL: https://issues.jboss.org/browse/ISPN-2580 > Project: Infinispan > Issue Type: Enhancement > Components: State transfer > Affects Versions: 5.2.0.Beta5 > Reporter: Radim Vansa > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 5.2.0.CR1 > > > When a new node joins large cluster filled with data, it gets the new CH and REBALANCE_START command, and requests data from all nodes at once (or almost all with even distribution of segments). It may be not able to handle this amount of transfers in parallel even at the JGroups level - this results in data sent to the node and discarded at the receiver, sent again and again. With a heavy congestion the node just buffers fragments of a message from one sender and never passes this up. > The number of StateRequestCommands(START_STATE_TRANSFER) should be limited so that the node is not congested. -- 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-2704) AsyncStoreTest.testRestrictionOnAddingToAsyncQueue still fails randomly

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2704?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2704: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/1570 > AsyncStoreTest.testRestrictionOnAddingToAsyncQueue still fails randomly > ----------------------------------------------------------------------- > > Key: ISPN-2704 > URL: https://issues.jboss.org/browse/ISPN-2704 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 5.2.0.CR2 > > > {code}testRestrictionOnAddingToAsyncQueue(org.infinispan.loaders.decorators.AsyncStoreTest) Time elapsed: 0.05 sec <<< FAILURE! > org.infinispan.CacheException: AsyncStore stopped; no longer accepting more entries. > at org.infinispan.loaders.decorators.AsyncStore$State.put(AsyncStore.java:401) > at org.infinispan.loaders.decorators.AsyncStore.put(AsyncStore.java:140) > at org.infinispan.loaders.decorators.AsyncStore.remove(AsyncStore.java:243) > at org.infinispan.loaders.decorators.AsyncStoreTest.doTestRemove(AsyncStoreTest.java:421) > at org.infinispan.loaders.decorators.AsyncStoreTest.testRestrictionOnAddingToAsyncQueue(AsyncStoreTest.java:147) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:46) > at org.testng.internal.InvokeMethodRunnable.run(InvokeMethodRunnable.java:37) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680){code} -- 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-1583) AbstractDelegatingAdvancedCache with(ClassLoader), withFlags(Flag...) logic is broken

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1583?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1583: ----------------------------------- Fix Version/s: 5.2.0.CR2 > AbstractDelegatingAdvancedCache with(ClassLoader), withFlags(Flag...) logic is broken > ------------------------------------------------------------------------------------- > > Key: ISPN-1583 > URL: https://issues.jboss.org/browse/ISPN-1583 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 5.1.0.BETA5 > Reporter: Paul Ferraro > Assignee: Galder Zamarreño > Fix For: 5.2.0.CR2, 5.2.0.Final > > > When the withFlags(...) logic was modified to use a DecoratedCache instead of thread-local storage, any caches already decorated with the AbstractDelegatingAdvancedCache(...) broke. > Take the following code: > AdvancedCache<K, V> baseCache; > AdvancedCache<K, V> customCache = new AbstractDelegatingAdvancedCache<K, V>(baseCache) { > public void clear() { > // custom clear logic > } > }; > customCache.withFlags(Flag.CACHE_MODE_LOCAL).clear(); > In the above statement, the flag is not applied. > The call to withFlags(...) returns a reference to customCache, and the reference to DecoratedCache containing the flags is lost to garbage collection. > In the case of with(ClassLoader) we have the opposite problem. > customCache.with(customClassLoader).clear(); > In the above statement, the native clear() method is invoked instead of my custom clear() method. with(ClassLoader) returns a reference to DecoratedCache. The clear() method then operates on baseCache, instead of customCache. -- 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 commented on ISPN-2632: ---------------------------------------- Getting TRACE with patched ER5 could be handy while we wait for ER6, which I assume should have CR1 in it. > 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-2601) Support Cross-Site replication in Server

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2601?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-2601: --------------------------------------- Yes, we can close this issue > Support Cross-Site replication in Server > ---------------------------------------- > > Key: ISPN-2601 > URL: https://issues.jboss.org/browse/ISPN-2601 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > -- 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-2596) Create unit test for ISPN-2574

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2596?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2596: -------------------------------- Assignee: Michal Linhard (was: Adrian Nistor) > Create unit test for ISPN-2574 > ------------------------------ > > Key: ISPN-2596 > URL: https://issues.jboss.org/browse/ISPN-2596 > Project: Infinispan > Issue Type: Task > Components: State transfer > Affects Versions: 5.2.0.Beta4 > Reporter: Adrian Nistor > Assignee: Michal Linhard > Fix For: 5.2.0.Final > > > ISPN-2574 was fixed and closed without a unit test, and we want one. -- 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-2601) Support Cross-Site replication in Server

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2601?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2601: ------------------------------------- Is this about exposing the xsite configuration within the AS? > Support Cross-Site replication in Server > ---------------------------------------- > > Key: ISPN-2601 > URL: https://issues.jboss.org/browse/ISPN-2601 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > -- 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-2690) SyncConsistentHash must implement Serializable

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2690?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-2690: ------------------------------------- So was it really SyncConsistentHash? The error message indicates TopologyAwareSyncConsistentHashFactory. > SyncConsistentHash must implement Serializable > ---------------------------------------------- > > Key: ISPN-2690 > URL: https://issues.jboss.org/browse/ISPN-2690 > Project: Infinispan > Issue Type: Bug > Components: Core API > Affects Versions: 5.2.0.Beta6 > Reporter: Erik Salter > Assignee: Erik Salter > Fix For: 5.2.0.CR1 > > > The SyncConsistentHash doesn't implement Serializable. Any such CH factory specified in the configuration will throw an error on startup: > 2013-01-06 01:05:20,008 ERROR [STDERR] (CacheStartThread,null,eigAllocation) Exception in thread "CacheStartThread,null,eigAllocation" > 2013-01-06 01:05:20,010 ERROR [STDERR] (CacheStartThread,null,eigAllocation) org.infinispan.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.start() throws java.lang.Exception on object of type StateTransferManagerImpl > 2013-01-06 01:05:20,010 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:205) > 2013-01-06 01:05:20,010 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:883) > 2013-01-06 01:05:20,010 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:654) > 2013-01-06 01:05:20,010 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:643) > 2013-01-06 01:05:20,010 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:546) > 2013-01-06 01:05:20,010 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:199) > 2013-01-06 01:05:20,010 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.CacheImpl.start(CacheImpl.java:557) > 2013-01-06 01:05:20,010 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:689) > 2013-01-06 01:05:20,010 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:652) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.manager.DefaultCacheManager.access$100(DefaultCacheManager.java:126) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.manager.DefaultCacheManager$1.run(DefaultCacheManager.java:574) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) Caused by: org.infinispan.CacheException: java.lang.RuntimeException: Failure to marshal argument(s) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.util.Util.rewrapAsCacheException(Util.java:539) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:184) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:515) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.topology.LocalTopologyManagerImpl.executeOnCoordinator(LocalTopologyManagerImpl.java:261) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.topology.LocalTopologyManagerImpl.join(LocalTopologyManagerImpl.java:101) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.statetransfer.StateTransferManagerImpl.start(StateTransferManagerImpl.java:117) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 2013-01-06 01:05:20,011 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > 2013-01-06 01:05:20,012 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 2013-01-06 01:05:20,012 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at java.lang.reflect.Method.invoke(Method.java:597) > 2013-01-06 01:05:20,012 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203) > 2013-01-06 01:05:20,012 ERROR [STDERR] (CacheStartThread,null,eigAllocation) ... 10 more > 2013-01-06 01:05:20,012 ERROR [STDERR] (CacheStartThread,null,eigAllocation) Caused by: java.lang.RuntimeException: Failure to marshal argument(s) > 2013-01-06 01:05:20,012 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.marshallCall(CommandAwareRpcDispatcher.java:279) > 2013-01-06 01:05:20,012 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:297) > 2013-01-06 01:05:20,012 ERROR [STDERR] (CacheStartThread,null,eigAllocation) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:177) > 2013-01-06 01:05:20,012 ERROR [STDERR] (CacheStartThread,null,eigAllocation) ... 19 more > 2013-01-06 01:05:20,012 ERROR [STDERR] (CacheStartThread,null,eigAllocation) Caused by: org.infinispan.marshall.NotSerializableException: org.infinispan.distribution.ch.TopologyAwareSyncConsistentHashFactory > 2013-01-06 01:05:20,013 ERROR [STDERR] (CacheStartThread,null,eigAllocation) Caused by: an exception which occurred: > in object org.infinispan.distribution.ch.TopologyAwareSyncConsistentHashFactory@5b6876ea > in object org.infinispan.topology.CacheJoinInfo@16b4417d > in object org.infinispan.topology.CacheTopologyControlCommand@31093d14 -- 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-2669) Add a Active-Passive Failover Strategy for Hot Rod client

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2669?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2669: ------------------------------------- Just a note, post ISPN-2643 and ISPN-2655, the hotrod client always goes to the main data owner for both reading and writing the data. > Add a Active-Passive Failover Strategy for Hot Rod client > --------------------------------------------------------- > > Key: ISPN-2669 > URL: https://issues.jboss.org/browse/ISPN-2669 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Ray Tsang > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > Currently HotRod client has only Round Robin request balancing strategy. There may be use cases where user needs to do an active-passive setup where all requests to go primary active node and only fallback to passive node when active is down. -- 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-2669) Add a Active-Passive Failover Strategy for Hot Rod client

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2669?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2669: -------------------------------- Fix Version/s: 5.3.0.Final > Add a Active-Passive Failover Strategy for Hot Rod client > --------------------------------------------------------- > > Key: ISPN-2669 > URL: https://issues.jboss.org/browse/ISPN-2669 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Ray Tsang > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > Currently HotRod client has only Round Robin request balancing strategy. There may be use cases where user needs to do an active-passive setup where all requests to go primary active node and only fallback to passive node when active is down. -- 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