April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5046) PartitionHandling: split during commit can leave the cache inconsistent after merge

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-5046?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-5046: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3358 > PartitionHandling: split during commit can leave the cache inconsistent after merge > ----------------------------------------------------------------------------------- > > Key: ISPN-5046 > URL: https://issues.jboss.org/browse/ISPN-5046 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.2.Final, 7.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.2.0.CR1 > > > Say we have a cluster ABCD; a transaction T was started on A, with B as the primary owner and C the backup owner. B and C both acknowledge the prepare, and the network splits into AB and CD right before A sends the commit command. Eventually A suspects C and D, but the commit still succeeds on B before C and D are suspected. And SuspectExceptions are ignored for commit commands, so the user won't see any error. > However, C will eventually suspect A and B. When the CD cache topology is installed, it will roll back transaction T. After the merge, both partitions are in degraded mode, so we assume that they both have the latest data and the key is never updated on C. > From C's point of view, this is very similar to ISPN-3421. The fix should also be similar, we could delay the transaction rollback on C until we get a confirmation from B that T was not committed there. Since B is inaccessible, it will eventually get a SuspectException and the CD cache topology, at which point the cache is in degraded mode and it can wait for a merge. On merge, it should check the status of the transaction on B again, and either commit or rollback based on what B did. > We also need to suspend the cleanup of completed transactions while the cache is in degraded mode, otherwise C might not find T on B after the merge. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5344) Caches inherit from default by mistake

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5344: ------------------------------------- Summary: Caches inherit from default by mistake Key: ISPN-5344 URL: https://issues.jboss.org/browse/ISPN-5344 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 7.2.0.Beta2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 7.2.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5343) Make eviction max-entries parameter configurable at runtime

by Duncan Doyle (JIRA)

Duncan Doyle created ISPN-5343: ---------------------------------- Summary: Make eviction max-entries parameter configurable at runtime Key: ISPN-5343 URL: https://issues.jboss.org/browse/ISPN-5343 Project: Infinispan Issue Type: Feature Request Components: Eviction Affects Versions: 7.2.0.Beta2 Environment: Infinispan 7/ JDG Reporter: Duncan Doyle I've got a use-case where I would like to be able to dynamically (at runtime) configure the max-entries parameter of my eviction configuration. This would allow to, for example, decrease the max-entries dynamically when my system starts running oom. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5251) Eviction configuration must be enforced in Near Caches

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5251?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5251: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1204759|https://bugzilla.redhat.com/show_bug.cgi?id=1204759] from ON_QA to VERIFIED > Eviction configuration must be enforced in Near Caches > ------------------------------------------------------ > > Key: ISPN-5251 > URL: https://issues.jboss.org/browse/ISPN-5251 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > If near cache is enabled, users should define the maximum number of elements to store in it. This is important to avoid clients running out of memory as a result of using near caching. In the current set up, when someone enables near caching, the local cache is unbounded. > The best approach is to force clients to define a maximum number of elements if enabling near caching. 0 would be unlimited. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5269) Process and generate component metadata for tests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5269?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5269: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1202477|https://bugzilla.redhat.com/show_bug.cgi?id=1202477] from VERIFIED to CLOSED > Process and generate component metadata for tests > ------------------------------------------------- > > Key: ISPN-5269 > URL: https://issues.jboss.org/browse/ISPN-5269 > Project: Infinispan > Issue Type: Enhancement > Components: Build process > Affects Versions: 7.2.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1, 7.1.2.Final > > > Currently it is not possible to use @Inject annotations in test classes because component metadata is not processed for test sources. It would be nice to have this (optionally) generated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5231) CacheNotifierImpl should wire the listener and converter with dependecies from ComponentRegistry

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5231?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5231: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1202477|https://bugzilla.redhat.com/show_bug.cgi?id=1202477] from VERIFIED to CLOSED > CacheNotifierImpl should wire the listener and converter with dependecies from ComponentRegistry > ------------------------------------------------------------------------------------------------ > > Key: ISPN-5231 > URL: https://issues.jboss.org/browse/ISPN-5231 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1, 7.2.0.Final, 7.1.2.Final > > > The wiring is already done for distributed iterators, so the same mechanism should be reused with filters that are used for events. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4450) RemoteStore uses wrong classloader with rawValues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4450?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4450: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1198726|https://bugzilla.redhat.com/show_bug.cgi?id=1198726] from VERIFIED to CLOSED > RemoteStore uses wrong classloader with rawValues > ------------------------------------------------- > > Key: ISPN-4450 > URL: https://issues.jboss.org/browse/ISPN-4450 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.2.Final > Reporter: Dennis Reed > Assignee: Tristan Tarrant > Fix For: 7.2.0.Beta1, 7.2.0.Final > > > RemoteStore uses the wrong classloader (Infinispan's classloader instead of the caller's classloader) during deserialization when rawValues=true is set. > It uses a GenericJBossMarshaller, which is hard-coded to only look in Infinispan's classloader). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[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 VERIFIED to CLOSED > Avoid invalid topology > ---------------------- > > Key: ISPN-5208 > URL: https://issues.jboss.org/browse/ISPN-5208 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Takayoshi Kimura > Assignee: Galder Zamarreño > Labels: jdg641 > Fix For: 7.2.0.Beta2, 7.2.0.Final > > Attachments: ISPN_5208.java > > > 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)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4322) AS Remote Client Module Integration Tests module fails with IBM JDK

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4322?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4322: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1101086|https://bugzilla.redhat.com/show_bug.cgi?id=1101086] from VERIFIED to CLOSED > AS Remote Client Module Integration Tests module fails with IBM JDK > ------------------------------------------------------------------- > > Key: ISPN-4322 > URL: https://issues.jboss.org/browse/ISPN-4322 > Project: Infinispan > Issue Type: Bug > Components: Integration > Affects Versions: 7.0.0.Alpha2, 7.0.0.Alpha3, 7.0.0.Alpha4 > Environment: IBM JDK, RHEL > Reporter: Vitalii Chepeliuk > Assignee: Vitalii Chepeliuk > Labels: testsuite_stability > > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Infinispan BOM .................................... SUCCESS [10.419s] > [INFO] Infinispan Common Parent .......................... SUCCESS [16.691s] > [INFO] Infinispan Commons ................................ SUCCESS [30.414s] > [INFO] Infinispan Core ................................... SUCCESS [1:20:24.345s] > [INFO] Parent pom for server modules ..................... SUCCESS [2.764s] > [INFO] Infinispan Server - Core Components ............... SUCCESS [1:39.998s] > [INFO] Infinispan Query DSL API .......................... SUCCESS [3.182s] > [INFO] Parent pom for cachestore modules ................. SUCCESS [1.421s] > [INFO] Infinispan JDBC CacheStore ........................ SUCCESS [7:13.024s] > [INFO] Parent pom for the Lucene integration modules ..... SUCCESS [1.302s] > [INFO] Infinispan integration with Lucene v.3.x .......... SUCCESS [1:22.270s] > [INFO] Infinispan Lucene Directory Implementation ........ SUCCESS [5.801s] > [INFO] Infinispan Query API .............................. SUCCESS [16:27.946s] > [INFO] Infinispan Tools .................................. SUCCESS [12.958s] > [INFO] Infinispan Remote Query Client .................... SUCCESS [3.958s] > [INFO] Infinispan Remote Query Server .................... SUCCESS [16.646s] > [INFO] Infinispan JPA CacheStore ......................... SUCCESS [54.680s] > [INFO] Infinispan Hot Rod Server ......................... SUCCESS [6:13.951s] > [INFO] Infinispan Hot Rod Client ......................... SUCCESS [9:17.450s] > [INFO] Parent pom for compatibility modules .............. SUCCESS [0.876s] > [INFO] infinispan-custom52x-store ........................ SUCCESS [33.084s] > [INFO] infinispan-adaptor52x ............................. SUCCESS [4:05.587s] > [INFO] Infinispan remote CacheStore ...................... SUCCESS [53.506s] > [INFO] Infinispan LevelDB CacheStore ..................... SUCCESS [1:19.592s] > [INFO] Infinispan REST Server ............................ SUCCESS [2:08.409s] > [INFO] Infinispan REST CacheStore ........................ SUCCESS [16.715s] > [INFO] Infinispan Memcached Server ....................... SUCCESS [2:22.394s] > [INFO] Infinispan RHQ Plugin ............................. SUCCESS [42.140s] > [INFO] Infinispan CLI Server ............................. SUCCESS [48.143s] > [INFO] Infinispan CLI Client ............................. SUCCESS [16.878s] > [INFO] Infinispan CDI support ............................ SUCCESS [1:24.550s] > [INFO] Infinispan AS/EAP modules for library ............. SUCCESS [18.319s] > [INFO] Infinispan AS/EAP modules for remote client ....... SUCCESS [2.329s] > [INFO] Integration tests: Security Tests ................. SUCCESS [2:11.936s] > [INFO] Integration tests: SecurityManager tests .......... SUCCESS [13.313s] > [INFO] Integration tests: AS Module Integration Tests .... SUCCESS [1:10.370s] > [INFO] Integration tests: AS Remote Client Module Integration Tests FAILURE [57.162s] > [INFO] Integration tests: Lucene Directory with Infinispan Query SUCCESS [23.074s] > [INFO] Integration tests: Infinispan compatibility mode .. SUCCESS [35.351s] > [INFO] Infinispan Distribution ........................... SUCCESS [1.090s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 2:26:30.994s > [INFO] Finished at: Fri May 23 21:38:55 EDT 2014 > [INFO] Final Memory: 227M/542M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (infinispan-server-shutdown) on project infinispan-as-module-remote-client-integrationtests: An Ant BuildException has occured: Execute failed: java.io.IOException: Cannot run program "/qa/tools/opt/amd64/ibm-java-70/bin/jps" (in directory "/mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/7e5d4f04/infinispan/integrationtests/as-integration-remote-client"): error=2, No such file or directory > [ERROR] around Ant part ...<exec executable="/qa/tools/opt/amd64/ibm-java-70/bin/jps" output="jps.pid" osfamily="unix"/>... @ 4:96 in /mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/7e5d4f04/infinispan/integrationtests/as-integration-remote-client/target/antrun/build-main.xml > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :infinispan-as-module-remote-client-integrationtests > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5199) TransportStackConfigurationIT failing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5199?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5199: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1202253|https://bugzilla.redhat.com/show_bug.cgi?id=1202253] from VERIFIED to CLOSED > TransportStackConfigurationIT failing > ------------------------------------- > > Key: ISPN-5199 > URL: https://issues.jboss.org/browse/ISPN-5199 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 7.1.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 7.2.0.Alpha1, 7.1.1.Final > > > TransportStackConfigurationIT.testTCPStackAttributes and TransportStackConfigurationIT.testUDPStackAttributes fails with: > {code} > org.junit.ComparisonFailure: expected:<[d]iscard> but was:<[D]iscard> > at org.junit.Assert.assertEquals(Assert.java:115) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.infinispan.server.test.transport.TransportStackConfigurationIT.assertMBeanAttributes(TransportStackConfigurationIT.java:76) > at org.infinispan.server.test.transport.TransportStackConfigurationIT.testUDPStackAttributes(TransportStackConfigurationIT.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2015