[JBoss JIRA] (ISPN-2714) org.infinispan.distexec.mapreduce.TopologyAwareTwoNodesMapReduceTest.testInvokeMapperCancellation test fails randomly
by Anna Manukyan (JIRA)
[ https://issues.jboss.org/browse/ISPN-2714?page=com.atlassian.jira.plugin.... ]
Anna Manukyan updated ISPN-2714:
--------------------------------
Git Pull Request: https://github.com/infinispan/infinispan/pull/1594 (was: https://github.com/infinispan/infinispan/pull/1592)
> org.infinispan.distexec.mapreduce.TopologyAwareTwoNodesMapReduceTest.testInvokeMapperCancellation test fails randomly
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2714
> URL: https://issues.jboss.org/browse/ISPN-2714
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Execution and Map/Reduce
> Affects Versions: 5.2.0.CR1
> Reporter: Anna Manukyan
> Assignee: Anna Manukyan
> Labels: testsuite_stability
>
> The test org.infinispan.distexec.mapreduce.TopologyAwareTwoNodesMapReduceTest.testInvokeMapperCancellation fails randomly on all environments.
> The error log is:
> {code}
> Error Message
> Expected exception java.util.concurrent.CancellationException but got java.lang.AssertionError: Mapper not cancelled, root cause org.jgroups.TimeoutException: timeout sending message to TopologyAwareTwoNodesMapReduceTest-NodeB-22523(test2)
> Stacktrace
> org.testng.TestException:
> Expected exception java.util.concurrent.CancellationException but got java.lang.AssertionError: Mapper not cancelled, root cause org.jgroups.TimeoutException: timeout sending message to TopologyAwareTwoNodesMapReduceTest-NodeB-22523(test2)
> at org.testng.internal.Invoker.handleInvocationResults(Invoker.java:1503)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:764)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> 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$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.AssertionError: Mapper not cancelled, root cause org.jgroups.TimeoutException: timeout sending message to TopologyAwareTwoNodesMapReduceTest-NodeB-22523(test2)
> at org.infinispan.distexec.mapreduce.SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation(SimpleTwoNodesMapReduceTest.java:106)
> 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:601)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
> ... 15 more
> {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
11 years, 11 months
[JBoss JIRA] (ISPN-2723) NPE using cache loader preload with Lucene directory
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2723?page=com.atlassian.jira.plugin.... ]
Work on ISPN-2723 started by Galder Zamarreño.
> NPE using cache loader preload with Lucene directory
> ----------------------------------------------------
>
> Key: ISPN-2723
> URL: https://issues.jboss.org/browse/ISPN-2723
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache, Loaders and Stores
> Affects Versions: 5.2.0.CR1
> Reporter: Christopher Wong
> Assignee: Galder Zamarreño
> Fix For: 5.2.0.Final
>
> Attachments: infinispan.log
>
>
> I am seeing an NPE that looks a lot like ISPN-1470, except this is happening in version 5.2.0.CR1 of Infinispan. I have configured Infinispan's Lucene directory provider for use in Hibernate Search. The Hibernate SessionFactory is configured with a JTA transaction manager. Starting with no index works fine, but if I shut down Tomcat (with shutdown.sh) and restart, a huge pile of exceptions occur, starting with an NPE. The cache configuration in infinispan.cfg.xml looks like the following. I will attach a log file excerpt with a sampling of the exceptions being logged. This only happens with distributed mode. Replicated mode is fine. I have seen this happen with both the Jdbm and file cache store.
> <namedCache
> name="LuceneIndexesData">
> <clustering
> mode="dist">
> <stateTransfer fetchInMemoryState="true"/>
> <sync
> replTimeout="50000" />
> <l1 enabled="false" />
> </clustering>
> <loaders shared="true" preload="true">
> <loader class="org.infinispan.loaders.file.FileCacheStore" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false">
> <properties>
> <property name="location" value="/some/path/.index/data" />
> </properties>
> </loader>
> </loaders>
> </namedCache>
--
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
11 years, 11 months
[JBoss JIRA] (ISPN-2723) NPE using cache loader preload with Lucene directory
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2723?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-2723:
----------------------------------------
Looks to me the NPE comes from stateTransferManager.getCacheTopology() returning null. That could potentially happen if preloading started before StateConsumerImpl.onTopologyUpdate() has executed.
That's indeed possible because CacheLoaderManagerImpl.preload() has @Start(priority = 56) and StateTransferManagerImpl.start() has @Start(priority = 60), so state transfer comes after preloading.
The issue seems to only happen when TX is injected, so although LuceneIndexesData cache does not appear transactional, I have the feeling that the default configuration has transactions enabled, which are being inherited by LuceneIndexesData.
@Christopher, can you attach the entire configuration file?
> NPE using cache loader preload with Lucene directory
> ----------------------------------------------------
>
> Key: ISPN-2723
> URL: https://issues.jboss.org/browse/ISPN-2723
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache, Loaders and Stores
> Affects Versions: 5.2.0.CR1
> Reporter: Christopher Wong
> Assignee: Galder Zamarreño
> Fix For: 5.2.0.Final
>
> Attachments: infinispan.log
>
>
> I am seeing an NPE that looks a lot like ISPN-1470, except this is happening in version 5.2.0.CR1 of Infinispan. I have configured Infinispan's Lucene directory provider for use in Hibernate Search. The Hibernate SessionFactory is configured with a JTA transaction manager. Starting with no index works fine, but if I shut down Tomcat (with shutdown.sh) and restart, a huge pile of exceptions occur, starting with an NPE. The cache configuration in infinispan.cfg.xml looks like the following. I will attach a log file excerpt with a sampling of the exceptions being logged. This only happens with distributed mode. Replicated mode is fine. I have seen this happen with both the Jdbm and file cache store.
> <namedCache
> name="LuceneIndexesData">
> <clustering
> mode="dist">
> <stateTransfer fetchInMemoryState="true"/>
> <sync
> replTimeout="50000" />
> <l1 enabled="false" />
> </clustering>
> <loaders shared="true" preload="true">
> <loader class="org.infinispan.loaders.file.FileCacheStore" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false">
> <properties>
> <property name="location" value="/some/path/.index/data" />
> </properties>
> </loader>
> </loaders>
> </namedCache>
--
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
11 years, 11 months
[JBoss JIRA] (ISPN-2574) Segment transfer not restarted if the owner fails
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2574?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-2574:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Segment transfer not restarted if the owner fails
> -------------------------------------------------
>
> Key: ISPN-2574
> URL: https://issues.jboss.org/browse/ISPN-2574
> Project: Infinispan
> Issue Type: Bug
> Components: State transfer
> Affects Versions: 5.2.0.Beta4
> Reporter: Radim Vansa
> Assignee: Adrian Nistor
> Priority: Critical
> Fix For: 5.2.0.Final
>
>
> Imagine this situation in distributed cache with 3 owners:
> 1) The segment X is owned by nodes A, B, C
> 2) Node B fails -> CH_UPDATE and then REBALANCE_START are broadcasted
> 3) Node D starts transfer of segment X from C
> 4) Node C fails -> another CH_UPDATE is broadcasted
> 5) D handes the CH_UPDATE and removes the transfer of segment X from C, but does not start another transfer from A
> The {{addedSegments}} does not contain the restarted transfer, because all transfers from write consistent hash are removed from it in the beginning - the segment is considered received here although the transfer is still in progress.
--
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
11 years, 11 months
[JBoss JIRA] (ISPN-2579) StateResponseCommand received after the node is removed from CH causes IllegalArgumentException
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2579?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-2579:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> StateResponseCommand received after the node is removed from CH causes IllegalArgumentException
> -----------------------------------------------------------------------------------------------
>
> Key: ISPN-2579
> URL: https://issues.jboss.org/browse/ISPN-2579
> Project: Infinispan
> Issue Type: Bug
> Components: State transfer
> Affects Versions: 5.2.0.Beta5
> Reporter: Radim Vansa
> Assignee: Adrian Nistor
> Priority: Minor
> Fix For: 5.2.0.Final
>
>
> When a node requests ST and then it receives a CH where this node is not a member, it sends ST request CANCEL_STATE_TRANSFER - however, if the StateResponseCommand is already on its way and reaches the node, it causes
> {code}
> java.lang.IllegalArgumentException: Node hyperion947-55285 is not a member
> at org.infinispan.distribution.ch.DefaultConsistentHash.getSegmentsForOwner(DefaultConsistentHash.java:102)
> at org.infinispan.statetransfer.StateConsumerImpl.applyState(StateConsumerImpl.java:272)
> at org.infinispan.statetransfer.StateResponseCommand.perform(StateResponseCommand.java:86)
> {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
11 years, 11 months
[JBoss JIRA] (ISPN-2723) NPE using cache loader preload with Lucene directory
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2723?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-2723:
-----------------------------------
Fix Version/s: 5.2.0.Final
> NPE using cache loader preload with Lucene directory
> ----------------------------------------------------
>
> Key: ISPN-2723
> URL: https://issues.jboss.org/browse/ISPN-2723
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache, Loaders and Stores
> Affects Versions: 5.2.0.CR1
> Reporter: Christopher Wong
> Assignee: Mircea Markus
> Fix For: 5.2.0.Final
>
> Attachments: infinispan.log
>
>
> I am seeing an NPE that looks a lot like ISPN-1470, except this is happening in version 5.2.0.CR1 of Infinispan. I have configured Infinispan's Lucene directory provider for use in Hibernate Search. The Hibernate SessionFactory is configured with a JTA transaction manager. Starting with no index works fine, but if I shut down Tomcat (with shutdown.sh) and restart, a huge pile of exceptions occur, starting with an NPE. The cache configuration in infinispan.cfg.xml looks like the following. I will attach a log file excerpt with a sampling of the exceptions being logged. This only happens with distributed mode. Replicated mode is fine. I have seen this happen with both the Jdbm and file cache store.
> <namedCache
> name="LuceneIndexesData">
> <clustering
> mode="dist">
> <stateTransfer fetchInMemoryState="true"/>
> <sync
> replTimeout="50000" />
> <l1 enabled="false" />
> </clustering>
> <loaders shared="true" preload="true">
> <loader class="org.infinispan.loaders.file.FileCacheStore" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false">
> <properties>
> <property name="location" value="/some/path/.index/data" />
> </properties>
> </loader>
> </loaders>
> </namedCache>
--
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
11 years, 11 months
[JBoss JIRA] (ISPN-2723) NPE using cache loader preload with Lucene directory
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2723?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño reassigned ISPN-2723:
--------------------------------------
Assignee: Galder Zamarreño (was: Mircea Markus)
> NPE using cache loader preload with Lucene directory
> ----------------------------------------------------
>
> Key: ISPN-2723
> URL: https://issues.jboss.org/browse/ISPN-2723
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache, Loaders and Stores
> Affects Versions: 5.2.0.CR1
> Reporter: Christopher Wong
> Assignee: Galder Zamarreño
> Fix For: 5.2.0.Final
>
> Attachments: infinispan.log
>
>
> I am seeing an NPE that looks a lot like ISPN-1470, except this is happening in version 5.2.0.CR1 of Infinispan. I have configured Infinispan's Lucene directory provider for use in Hibernate Search. The Hibernate SessionFactory is configured with a JTA transaction manager. Starting with no index works fine, but if I shut down Tomcat (with shutdown.sh) and restart, a huge pile of exceptions occur, starting with an NPE. The cache configuration in infinispan.cfg.xml looks like the following. I will attach a log file excerpt with a sampling of the exceptions being logged. This only happens with distributed mode. Replicated mode is fine. I have seen this happen with both the Jdbm and file cache store.
> <namedCache
> name="LuceneIndexesData">
> <clustering
> mode="dist">
> <stateTransfer fetchInMemoryState="true"/>
> <sync
> replTimeout="50000" />
> <l1 enabled="false" />
> </clustering>
> <loaders shared="true" preload="true">
> <loader class="org.infinispan.loaders.file.FileCacheStore" fetchPersistentState="false" ignoreModifications="false" purgeOnStartup="false">
> <properties>
> <property name="location" value="/some/path/.index/data" />
> </properties>
> </loader>
> </loaders>
> </namedCache>
--
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
11 years, 11 months
[JBoss JIRA] (ISPN-2421) Optimise the call to LocalTransaction.getCommitNodes
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2421?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-2421:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Optimise the call to LocalTransaction.getCommitNodes
> ----------------------------------------------------
>
> Key: ISPN-2421
> URL: https://issues.jboss.org/browse/ISPN-2421
> Project: Infinispan
> Issue Type: Sub-task
> Affects Versions: 5.2.0.Beta2
> Reporter: Mircea Markus
> Assignee: Adrian Nistor
> Fix For: 5.2.0.Final
>
>
> Once ISPN-2420 is in place, we can optimise LocaTransaction.getCommitNodes to only calculate the destination IFF the topologyId has changed between the tx being prepared and now.
> And we should also remove TransactionTable.useStrictTopologyIdComparison() and simplify all code that relied on it in AbstractTxLockingInterceptor.
--
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
11 years, 11 months
