[JBoss JIRA] (ISPN-3352) Issues with the M/Rs intermediate cache shut down
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3352?page=com.atlassian.jira.plugin.... ]
Mircea Markus commented on ISPN-3352:
-------------------------------------
Should also fix some intermittent failures in XyzFourNodesMapReduceTest classes
> Issues with the M/Rs intermediate cache shut down
> -------------------------------------------------
>
> Key: ISPN-3352
> URL: https://issues.jboss.org/browse/ISPN-3352
> Project: Infinispan
> Issue Type: Feature Request
> Components: Distributed Execution and Map/Reduce
> Affects Versions: 5.3.0.Final
> Reporter: Mircea Markus
> Assignee: Mircea Markus
> Fix For: 6.0.0.Alpha2, 6.0.0.Final
>
>
> The intermediate cache that is created for a distributed map/reduce phase calls cache.clear() before shutting down. This is a distributed call and might result in a timeout given that some of the cache instances on remote nodes are shutting down whilst processing the clear response.
> This clear invocation should be local.
--
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, 2 months
[JBoss JIRA] (ISPN-3352) Issues with the M/Rs intermediate cache shut down
by Mircea Markus (JIRA)
Mircea Markus created ISPN-3352:
-----------------------------------
Summary: Issues with the M/Rs intermediate cache shut down
Key: ISPN-3352
URL: https://issues.jboss.org/browse/ISPN-3352
Project: Infinispan
Issue Type: Feature Request
Components: Distributed Execution and Map/Reduce
Affects Versions: 5.3.0.Final
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 6.0.0.Alpha2, 6.0.0.Final
The intermediate cache that is created for a distributed map/reduce phase calls cache.clear() before shutting down. This is a distributed call and might result in a timeout given that some of the cache instances on remote nodes are shutting down whilst processing the clear response.
This clear invocation should be local.
--
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, 2 months
[JBoss JIRA] (ISPN-2896) org.infinispan.lucene.DirectoryOnMultipleCachesTest.verifyIntendedLockCachesUsage fails randomly
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2896?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2896:
-----------------------------------------------
Richard Janík <rjanik(a)redhat.com> made a comment on [bug 921984|https://bugzilla.redhat.com/show_bug.cgi?id=921984]
Seen in 6.1.1.ER3 with Infinispan 5.2.7.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Infi...
> org.infinispan.lucene.DirectoryOnMultipleCachesTest.verifyIntendedLockCachesUsage fails randomly
> ------------------------------------------------------------------------------------------------
>
> Key: ISPN-2896
> URL: https://issues.jboss.org/browse/ISPN-2896
> Project: Infinispan
> Issue Type: Bug
> Components: Lucene Directory
> Affects Versions: 5.2.2.Final
> Reporter: Anna Manukyan
> Assignee: Sanne Grinovero
> Labels: stable_embedded_query
> Fix For: 5.3.0.CR1
>
>
> org.infinispan.lucene.DirectoryOnMultipleCachesTest.verifyIntendedLockCachesUsage fails randomly. The error message is:
> {code}
> java.lang.AssertionError
> at org.infinispan.lucene.DirectoryOnMultipleCachesTest.verifyIntendedLockCachesUsage(DirectoryOnMultipleCachesTest.java:96)
> 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)
> 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)
> {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, 2 months