March 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5208) Avoid invalid topology

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5208?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5208: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1190001|https://bugzilla.redhat.com/show_bug.cgi?id=1190001] from MODIFIED to ON_QA > Avoid invalid topology > ---------------------- > > Key: ISPN-5208 > URL: https://issues.jboss.org/browse/ISPN-5208 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Reporter: Takayoshi Kimura > Assignee: Galder Zamarreño > Labels: jdg641 > Fix For: 7.2.0.Final > > > We've seen some invalid topology propagated to client and it causes ArrayIndexOutOfBoundsException: > {noformat} > Caused by: java.lang.ArrayIndexOutOfBoundsException: 0 > at org.infinispan.client.hotrod.impl.transport.tcp.RoundRobinBalancingStrategy.getServerByIndex(RoundRobinBalancingStrategy.java:68) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > at org.infinispan.client.hotrod.impl.transport.tcp.RoundRobinBalancingStrategy.nextServer(RoundRobinBalancingStrategy.java:44) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.nextServer(TcpTransportFactory.java:220) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.getTransport(TcpTransportFactory.java:194) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > at org.infinispan.client.hotrod.impl.operations.FaultTolerantPingOperation.getTransport(FaultTolerantPingOperation.java:27) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:48) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.ping(RemoteCacheImpl.java:535) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > at org.infinispan.client.hotrod.RemoteCacheManager.ping(RemoteCacheManager.java:635) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > at org.infinispan.client.hotrod.RemoteCacheManager.createRemoteCache(RemoteCacheManager.java:616) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:527) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > at org.infinispan.client.hotrod.RemoteCacheManager.getCache(RemoteCacheManager.java:523) [infinispan-client-hotrod-6.1.0.Final-redhat-4.jar:6.1.0.Final-redhat-4] > {noformat} > {noformat} > Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0 > at org.infinispan.client.hotrod.impl.consistenthash.SegmentConsistentHash.getServer(SegmentConsistentHash.java:33) > at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.getTransport(TcpTransportFactory.java:204) > at org.infinispan.client.hotrod.impl.operations.AbstractKeyOperation.getTransport(AbstractKeyOperation.java:40) > at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:48) > at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:237) > at org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:79) > at sample.Main.main(Main.java:16) > {noformat} > It happens on both Hot Rod 2 and 1.3 clients. > It's really hard to reproduce this state and we don't have a consistent way to reproduce it. However when this happens there is always view change happening so it's related to view change. > Judging from the stack trace, the client receives numOwners=0 or numSegments=0 topology from the server. > Also we are unable to find to recover this situation. Rebooting random nodes don't help and keep getting this exceptions on client side. > Until we can find the root cause, I think it's better to add a guard to avoid this kind invalid topology stored in the server side and propagated to the clients. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5174) Transaction cannot be recommitted after ownership changes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5174?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5174: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1185779|https://bugzilla.redhat.com/show_bug.cgi?id=1185779] from MODIFIED to ON_QA > Transaction cannot be recommitted after ownership changes > --------------------------------------------------------- > > Key: ISPN-5174 > URL: https://issues.jboss.org/browse/ISPN-5174 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.1.0.CR2 > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > > Once transaction is completed, it cannot commit again. If it should commit more keys since it has become an owner of some new keys modified in this transaction, it just ignores the further commit. > There is a race with state transfer which can bring an old value (with StateResponseCommand sent before it is commited) but the value is not set by the ongoing transaction either. > This results with stale value stored on one node. > In my case, The problematic part is transaction <edg-perf01-62141>:15066 (consisting of 10 modifications) which got prepared and committed on edg-perf04 in topology 25. Before the originator finishes, topology changes and 04 requests ongoing transactions: > {code} > 11:06:11,369 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (transport-thread-17) Replication task sending StateRequestCommand{cache=testCache, origin=edg-perf04-35097, type=GET_TRANSACTIONS, topologyId=28, segments=[275, 1, 278, 9, 282, 286, 17, 259, 25, 267, 171, 169, 33, 306, 175, 173, 310, 172, 314, 41, 167, 165, 318, 187, 290, 49, 185, 191, 294, 189, 179, 298, 57, 177, 183, 302, 181, 343, 205, 201, 338, 203, 336, 351, 197, 349, 199, 347, 193, 345, 195, 326, 85, 87, 322, 93, 332, 95, 330, 89, 91, 103, 101, 99, 506, 97, 105, 357, 359, 353, 355, 361]} to single recipient edg-perf01-62141 with response mode GET_ALL > 11:06:11,495 DEBUG [org.infinispan.statetransfer.StateConsumerImpl] (transport-thread-17) Applying 6 transactions for cache testCache transferred from node edg-perf01-62141 > {code} > However I don't see how these are applied, since PrepareCommand is not created again - from the code I see only that backup locks are added. Not sure if the transaction is registered at all, since it was already completed on this node (but at that time it did not own key_00000000000002EB). > After originator stores the entry, it sends one more CommitCommand with topology 28: > {code} > 11:06:11,619 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (DefaultStressor-2) Replication task sending CommitCommand {gtx=GlobalTransaction:<edg-perf01-62141>:15066:local, cacheName='testCache', topologyId=28} to addresses [edg-perf03-20530, edg-perf04-35097] with response mode GET_ALL > {code} > 04 receives several CommitCommands (both from originator and forwards), but all of them are ignored as the transaction is completed. > I don't see the logs where state transfer is assembled, but it's probably before the entry is stored on originator as the state transfer contains the old entry: > {code} > 11:06:13,449 TRACE [org.infinispan.statetransfer.StateConsumerImpl] (remote-thread-91) Received chunk with keys [key_000000000000065B, key_00000000000006BE, key_FFFFFFFFFFFFE62F, key_0000000000001F42, key_000000000000027B, key_000000000000159D, key_00000000000002EB, key_00000000000002BB] for segment 343 of cache testCache from node edg-perf01-62141 > 11:06:13,454 TRACE [org.infinispan.container.DefaultDataContainer] (remote-thread-91) Store ImmortalCacheEntry{key=key_00000000000002EB, value=[2 #7: 366, 544, 576, 804, 1061, 1181, 1290, ]} in container > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5283) Hot Rod client does not update the cluster view for the client after a complete shutdown of all servers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5283?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5283: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1200360|https://bugzilla.redhat.com/show_bug.cgi?id=1200360] from MODIFIED to ON_QA > Hot Rod client does not update the cluster view for the client after a complete shutdown of all servers > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-5283 > URL: https://issues.jboss.org/browse/ISPN-5283 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.2.Final, 7.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > If a Hot Rod client is connected to two (or more) servers and these servers are stopped the client will not continue to work until this last server is back online. > But even if the client is able to continue, the client will not receive updated cluster topology. > Therefor there is no loadbalacing and failover after this point until the client is restarted. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5072) MapExternalizer no longer needs to extend InstanceReusingAdvancedExternalizer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5072?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5072: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1200514|https://bugzilla.redhat.com/show_bug.cgi?id=1200514] from MODIFIED to ON_QA > MapExternalizer no longer needs to extend InstanceReusingAdvancedExternalizer > ----------------------------------------------------------------------------- > > Key: ISPN-5072 > URL: https://issues.jboss.org/browse/ISPN-5072 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.1.0.Alpha1 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.1.0.Beta1, 7.1.0.Final > > > The MapExternalizer originally extended InstanceReusingAdvancedExternalizer to allow for the CacheStatusResponse class to properly reuse values. However with ISPN-3561 we no longer use just a Map but also a ManagerStatusResponse so we only need the Externalizer for that class to extend InstanceReusingAdvancedExternalizer. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5300) CacheEventFilterAsKeyValueFilter must pass the value and metadata as 'new' to the underlying CacheEventFilter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5300?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5300: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1202409|https://bugzilla.redhat.com/show_bug.cgi?id=1202409] from MODIFIED to ON_QA > CacheEventFilterAsKeyValueFilter must pass the value and metadata as 'new' to the underlying CacheEventFilter > ------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5300 > URL: https://issues.jboss.org/browse/ISPN-5300 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1, 7.2.0.Final, 7.1.2.Final > > > Current implementetion passes the value as old value to the wrapped filter. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5283) Hot Rod client does not update the cluster view for the client after a complete shutdown of all servers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5283?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5283: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1200360|https://bugzilla.redhat.com/show_bug.cgi?id=1200360] from POST to MODIFIED > Hot Rod client does not update the cluster view for the client after a complete shutdown of all servers > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-5283 > URL: https://issues.jboss.org/browse/ISPN-5283 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.2.Final, 7.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > If a Hot Rod client is connected to two (or more) servers and these servers are stopped the client will not continue to work until this last server is back online. > But even if the client is able to continue, the client will not receive updated cluster topology. > Therefor there is no loadbalacing and failover after this point until the client is restarted. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5288) Options for configuring various providers in cloud cache store

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5288?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5288: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.2.0.Beta2 7.2.0.Final Resolution: Done > Options for configuring various providers in cloud cache store > -------------------------------------------------------------- > > Key: ISPN-5288 > URL: https://issues.jboss.org/browse/ISPN-5288 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > Make sure that Cloud cache provider can work with various blob stores. > * AWS S3 doesn't allow underscores in bucket names (currently bucket name is create as {{$containername_cachename}}) > * Some providers need to configure API endpoint (e.g. Swift) > * Some providers need to configure additional properties (overriders) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5283) Hot Rod client does not update the cluster view for the client after a complete shutdown of all servers

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5283?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5283: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1200360|https://bugzilla.redhat.com/show_bug.cgi?id=1200360] from ASSIGNED to POST > Hot Rod client does not update the cluster view for the client after a complete shutdown of all servers > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-5283 > URL: https://issues.jboss.org/browse/ISPN-5283 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 6.0.2.Final, 7.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > If a Hot Rod client is connected to two (or more) servers and these servers are stopped the client will not continue to work until this last server is back online. > But even if the client is able to continue, the client will not receive updated cluster topology. > Therefor there is no loadbalacing and failover after this point until the client is restarted. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5072) MapExternalizer no longer needs to extend InstanceReusingAdvancedExternalizer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5072?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5072: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1200525|https://bugzilla.redhat.com/show_bug.cgi?id=1200525] from POST to MODIFIED > MapExternalizer no longer needs to extend InstanceReusingAdvancedExternalizer > ----------------------------------------------------------------------------- > > Key: ISPN-5072 > URL: https://issues.jboss.org/browse/ISPN-5072 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.1.0.Alpha1 > Reporter: William Burns > Assignee: William Burns > Fix For: 7.1.0.Beta1, 7.1.0.Final > > > The MapExternalizer originally extended InstanceReusingAdvancedExternalizer to allow for the CacheStatusResponse class to properly reuse values. However with ISPN-3561 we no longer use just a Map but also a ManagerStatusResponse so we only need the Externalizer for that class to extend InstanceReusingAdvancedExternalizer. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4791) Create a project skeleton for admin management console

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4791?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic resolved ISPN-4791. --------------------------------------- Fix Version/s: 7.2.0.Final Resolution: Done Closing as we have created project already at https://github.com/infinispan/infinispan-management-console > Create a project skeleton for admin management console > ------------------------------------------------------- > > Key: ISPN-4791 > URL: https://issues.jboss.org/browse/ISPN-4791 > Project: Infinispan > Issue Type: Sub-task > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Fix For: 7.2.0.Final > > > We need to create HTML5/Bootstrap/AngularJS project skeleton for our admin management console. We should setup grunt, bower, yeoman etc; write a short manual for building project, running it locally and so on. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2015