[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 1202341|https://bugzilla.redhat.com/show_bug.cgi?id=1202341] 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, 7.1.1.Final
> Reporter: Radim Vansa
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.2.0.Beta2, 7.2.0.Final
>
>
> 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)
10 years, 11 months
[JBoss JIRA] (ISPN-2183) Add the ability to fetch a set of keys at once (getAll)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2183?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2183:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1198556|https://bugzilla.redhat.com/show_bug.cgi?id=1198556] from MODIFIED to ON_QA
> Add the ability to fetch a set of keys at once (getAll)
> -------------------------------------------------------
>
> Key: ISPN-2183
> URL: https://issues.jboss.org/browse/ISPN-2183
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Reporter: Mircea Markus
> Assignee: William Burns
> Priority: Minor
> Fix For: 7.2.0.CR1
>
>
> When a transaction knows in advance about the set of keys it needs to read, this cache.getAll(k1,k2,..kn) method can bring a some performance improvement:
> 1. all the keys can be fetched from remote nodes in parallel
> 2. keys that map to the same node can be grouped and fetched in the same RPC request
>
> Note that 1. can be be achieved even at this time by using Cache.getAsync(K) method - that's not as elegant though as it requires the user to write the code the code that waits on the Future objects that are returned.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (ISPN-4258) *MassIndexing.testReindexing test fails randomly on RHEL7
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4258?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4258:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1208162|https://bugzilla.redhat.com/show_bug.cgi?id=1208162] from MODIFIED to ON_QA
> *MassIndexing.testReindexing test fails randomly on RHEL7
> -----------------------------------------------------------
>
> Key: ISPN-4258
> URL: https://issues.jboss.org/browse/ISPN-4258
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 7.0.0.Alpha3
> Reporter: Vitalii Chepeliuk
> Assignee: Gustavo Fernandes
> Labels: testsuite_stability
> Fix For: 7.0.0.Beta2
>
> Attachments: MassIndexingTests.zip
>
>
> Following tests fail with assertion error
> DistProgrammaticMassIndexTest.testReindexing
> TopologyAwareDistMassIndexingTest.testReindexing
> DistributedMassIndexingTest.testReindexing
> DistributedMassIndexingViaJmxTest.testReindexing
> DistributedMassIndexingViaJmxTest.createBeforeClass
> {noformat}
> java.lang.AssertionError: expected:<3> but was:<0>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.infinispan.query.distributed.DistributedMassIndexingTest.verifyFindsCar(DistributedMassIndexingTest.java:89)
> at org.infinispan.query.distributed.DistributedMassIndexingTest.verifyFindsCar(DistributedMassIndexingTest.java:80)
> at org.infinispan.query.distributed.DistributedMassIndexingTest.testReindexing(DistributedMassIndexingTest.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[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 1211997|https://bugzilla.redhat.com/show_bug.cgi?id=1211997] from MODIFIED to ON_QA
> 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
> Fix For: 7.2.0.CR1, 7.2.0.Final
>
>
> {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)
10 years, 11 months