[JBoss JIRA] (ISPN-4039) DistSyncTxFuncTest and its subclasses fail all the time
by Dan Berindei (JIRA)
Dan Berindei created ISPN-4039:
----------------------------------
Summary: DistSyncTxFuncTest and its subclasses fail all the time
Key: ISPN-4039
URL: https://issues.jboss.org/browse/ISPN-4039
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Core
Affects Versions: 6.0.1.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 7.0.0.Alpha1
All the methods in DistSyncTxFuncTest and its subclasses DistAsyncTxFuncTest, DistSyncTxUnsafeFuncTest, DistAsyncTxUnsafeFuncTest, fail in TeamCity.
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-4036) StateConsumerImpl.isKeyUpdated searches for the key in the values collection
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-4036?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo commented on ISPN-4036:
-----------------------------------
[~dan.berindei] although this is simple to solve, I dropped the updatedKeys in StateConsumer and I used a shared structure for NBST and X-Site ST.
> StateConsumerImpl.isKeyUpdated searches for the key in the values collection
> ----------------------------------------------------------------------------
>
> Key: ISPN-4036
> URL: https://issues.jboss.org/browse/ISPN-4036
> Project: Infinispan
> Issue Type: Bug
> Components: Core, State Transfer
> Affects Versions: 6.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Fix For: 7.0.0.Alpha1
>
>
> Introduced by the ISPN-3443 fix. I changed the {{updatedKeys}} HashSet to be an EquivalendConcurrentHashMap, but I forgot to change the {{contains(key)}} call to {{containsKey(key)}}. Since we use the same value for all the keys, it means state transfer might skip more keys than it should have.
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-4038) CustomFailurePolicyTxTest.testPrepareFailure random failures
by Dan Berindei (JIRA)
Dan Berindei created ISPN-4038:
----------------------------------
Summary: CustomFailurePolicyTxTest.testPrepareFailure random failures
Key: ISPN-4038
URL: https://issues.jboss.org/browse/ISPN-4038
Project: Infinispan
Issue Type: Bug
Components: Cross-Site Replication, Test Suite - Core
Affects Versions: 6.0.1.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 7.0.0.Alpha1
http://ci.infinispan.org/viewLog.html?buildId=5935&tab=buildResultsDiv&bu...
{noformat}
java.lang.AssertionError: expected:<0> but was:<1>
at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245)
at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252)
at org.infinispan.xsite.backupfailure.tx.BaseBackupTxFailureTest.testPrepareFailure(BaseBackupTxFailureTest.java:45)
at org.infinispan.xsite.backupfailure.tx.CustomFailurePolicyTxTest.testPrepareFailure(CustomFailurePolicyTxTest.java:37)
{noformat}
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-3815) Tests which extends persistence.ParallelIterationTest fail randomly on all environments
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-3815?page=com.atlassian.jira.plugin.... ]
Dan Berindei resolved ISPN-3815.
--------------------------------
Assignee: Dan Berindei (was: Mircea Markus)
Resolution: Duplicate Issue
Duplicate of ISPN-3594
> Tests which extends persistence.ParallelIterationTest fail randomly on all environments
> -----------------------------------------------------------------------------------------
>
> Key: ISPN-3815
> URL: https://issues.jboss.org/browse/ISPN-3815
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 6.0.0.Final, 6.0.1.Final
> Reporter: Vitalii Chepeliuk
> Assignee: Dan Berindei
> Labels: testsuite_stability
>
> Following tests fail
> LevelDBParallelIterationTest
> JdbcBinaryStoreParallelIterationTest
> SingleFileStoreParallelIterationTest
> java.lang.AssertionError: expected [5] but found [4]
> at org.testng.Assert.fail(Assert.java:89)
> at org.testng.Assert.failNotEquals(Assert.java:489)
> at org.testng.Assert.assertEquals(Assert.java:118)
> at org.testng.Assert.assertEquals(Assert.java:365)
> at org.testng.Assert.assertEquals(Assert.java:375)
> at org.infinispan.persistence.ParallelIterationTest.runIterationTest(ParallelIterationTest.java:117)
> at org.infinispan.persistence.ParallelIterationTest.testParallelIteration(ParallelIterationTest.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> * on RHEL
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
> * on Windows
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-3942) HotRod client keep trying recover a connection to a cluster member after shutdown
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3942?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3942:
-----------------------------------------------
Radim Vansa <rvansa(a)redhat.com> changed the Status of [bug 1059277|https://bugzilla.redhat.com/show_bug.cgi?id=1059277] from ON_QA to ASSIGNED
> HotRod client keep trying recover a connection to a cluster member after shutdown
> ---------------------------------------------------------------------------------
>
> Key: ISPN-3942
> URL: https://issues.jboss.org/browse/ISPN-3942
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Environment: Infinispan server with HotRod client in server-client mode and replicated caches.
> Reporter: Wolf-Dieter Fink
> Assignee: Pedro Ruivo
> Priority: Critical
> Labels: clustered, hotrod, hotrod-java-client
> Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
> Attachments: hotrod-client.log
>
>
> If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed.
> There is only a replicated cache configured.
> From the server-logfile the new cluster view is established
> 16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered]
> There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server.
> This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason.
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-3942) HotRod client keep trying recover a connection to a cluster member after shutdown
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3942?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3942:
-----------------------------------------------
Radim Vansa <rvansa(a)redhat.com> changed the Status of [bug 1059277|https://bugzilla.redhat.com/show_bug.cgi?id=1059277] from POST to ON_QA
> HotRod client keep trying recover a connection to a cluster member after shutdown
> ---------------------------------------------------------------------------------
>
> Key: ISPN-3942
> URL: https://issues.jboss.org/browse/ISPN-3942
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Environment: Infinispan server with HotRod client in server-client mode and replicated caches.
> Reporter: Wolf-Dieter Fink
> Assignee: Pedro Ruivo
> Priority: Critical
> Labels: clustered, hotrod, hotrod-java-client
> Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
> Attachments: hotrod-client.log
>
>
> If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed.
> There is only a replicated cache configured.
> From the server-logfile the new cluster view is established
> 16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered]
> There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server.
> This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason.
--
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
12 years, 1 month
[JBoss JIRA] (ISPN-4021) Allow each Map/Reduce task to use a different cache configuration
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-4021?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic commented on ISPN-4021:
-------------------------------------------
Dan, we have two options here:
a) we can pass intermediate cache directly to MapReduceTask and thus force correct typing
b) pass the cache name only
Option b) gives more flexibility in the future if things change internally while option a) minimizes potential errors on the behalf of user at the expense of flexibility a) has.
What should we do?
> Allow each Map/Reduce task to use a different cache configuration
> -----------------------------------------------------------------
>
> Key: ISPN-4021
> URL: https://issues.jboss.org/browse/ISPN-4021
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Distributed Execution and Map/Reduce
> Affects Versions: 6.0.1.Final
> Reporter: Dan Berindei
> Assignee: Vladimir Blagojevic
> Fix For: 7.0.0.Final
>
>
> Some Map/Reduce tasks may need a cache store and eviction, some may not. Each task should be able to use its own cache configuration.
--
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
12 years, 1 month