January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2507) @DataRehashed event is not triggered

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2507?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2507: ----------------------------------- Fix Version/s: 5.2.0.CR3 (was: 5.2.0.Final) > @DataRehashed event is not triggered > ------------------------------------ > > Key: ISPN-2507 > URL: https://issues.jboss.org/browse/ISPN-2507 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta2 > Reporter: Anna Manukyan > Assignee: Dan Berindei > Priority: Critical > Fix For: 5.2.0.CR3 > > > The case is the following: > There is 2 node cluster. The first is up and running. The second node starts and puts data into the cache. The cache is configured with DIST_ASYNC clustering mode. > The test checks that the data is rehashed, i.e. state transfer has done, but the @DataRehashed event was not triggered. > You can find the failing test results here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-jdbc-cache-sto... > and here: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-jdbc-cache-sto... > The test is located here: > https://svn.devel.redhat.com/repos/jboss-qa/jdg/jdg-functional-tests/trun... > Best regards, > Anna. -- 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
0
0 / 0

[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: ----------------------------------- Fix Version/s: 5.2.0.CR3 (was: 5.2.0.Final) > 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.CR3 > > > 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2596) Create unit test for ISPN-2574

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2596?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2596: ----------------------------------- Fix Version/s: 5.2.0.CR3 (was: 5.2.0.Final) > Create unit test for ISPN-2574 > ------------------------------ > > Key: ISPN-2596 > URL: https://issues.jboss.org/browse/ISPN-2596 > Project: Infinispan > Issue Type: Task > Components: State transfer > Affects Versions: 5.2.0.Beta4 > Reporter: Adrian Nistor > Assignee: Michal Linhard > Fix For: 5.2.0.CR3 > > > ISPN-2574 was fixed and closed without a unit test, and we want one. -- 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
0
0 / 0

[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: ----------------------------------- Fix Version/s: 5.2.0.CR3 (was: 5.2.0.Final) > 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.CR3 > > > 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2401) StateTransferManager.isStateTransferInProgress/ForKey return false at the start of state transfer

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2401?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2401: ----------------------------------- Fix Version/s: 5.2.0.CR3 (was: 5.2.0.Final) > StateTransferManager.isStateTransferInProgress/ForKey return false at the start of state transfer > -------------------------------------------------------------------------------------------------- > > Key: ISPN-2401 > URL: https://issues.jboss.org/browse/ISPN-2401 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta2 > Reporter: Dan Berindei > Assignee: Adrian Nistor > Fix For: 5.2.0.CR3 > > > They only check the segments that are in progress, so they return false if state transfer started but didn't add any segment to the in-progress list yet. > If isStateTransferInProgressForKey is fixed, DistributionManagerImpl.getLocality should be changed to use it again. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2723) NPE using cache loader preload with Lucene directory

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2723?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2723: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.2.0.CR3 Resolution: Done > 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.CR3, 5.2.0.Final > > Attachments: infinispan.cfg.xml, 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2748) ExternalizerTable should look for annotations when not finding an externalizer in its writers

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2748?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2748: ----------------------------------- Fix Version/s: 5.2.0.CR3 > ExternalizerTable should look for annotations when not finding an externalizer in its writers > --------------------------------------------------------------------------------------------- > > Key: ISPN-2748 > URL: https://issues.jboss.org/browse/ISPN-2748 > Project: Infinispan > Issue Type: Bug > Components: Marshalling > Affects Versions: 5.1.2.FINAL, 5.2.0.CR2 > Reporter: Randall Hauch > Assignee: Galder Zamarreño > Fix For: 5.2.0.CR3, 5.2.0.Final > > > The {{ExternalizerTable.isMarshallableCandidate(Object)}} method currently looks in its writers to see if there is an externalizer for the supplied class. However, under certain circumstances, a user-friendly externalizer is not registered. So this method should also look for annotations to see if the class has a user-friendly externalizer. > See MODE-1769 for background. -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2664) DistSyncCacheStoreNotSharedNotConcurrentTest.testAtomicPutIfAbsentFromNonOwner fails randomly

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2664?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-2664: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.2.0.CR3 Resolution: Done > DistSyncCacheStoreNotSharedNotConcurrentTest.testAtomicPutIfAbsentFromNonOwner fails randomly > --------------------------------------------------------------------------------------------- > > Key: ISPN-2664 > URL: https://issues.jboss.org/browse/ISPN-2664 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 5.2.0.CR3, 5.2.0.Final > > Attachments: testAtomicPutIfAbsentFromNonOwner-0.log > > > {code}testAtomicPutIfAbsentFromNonOwner(org.infinispan.distribution.DistSyncCacheStoreNotSharedNotConcurrentTest) Time elapsed: 0.004 sec <<< FAILURE! > java.lang.AssertionError > at org.infinispan.distribution.DistSyncCacheStoreNotSharedTest.testAtomicPutIfAbsentFromNonOwner(DistSyncCacheStoreNotSharedTest.java:297) > 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:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680){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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2757) ReplaceCommand REPL mode cluster does not perform any modifications if the entry was not yet transfered during rehashing

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-2757: ----------------------------------- Summary: ReplaceCommand REPL mode cluster does not perform any modifications if the entry was not yet transfered during rehashing Key: ISPN-2757 URL: https://issues.jboss.org/browse/ISPN-2757 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.2.0.Beta5 Reporter: Adrian Nistor Assignee: Adrian Nistor Priority: Blocker Fix For: 5.2.0.Final The local data container does not have the entry yet so the ReplaceCommand fails. See BaseDistStateTransferConsistencyTest.testReplace() and BaseReplStateTransferConsistencyTest.testReplace(). -- 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
0
0 / 0

[JBoss JIRA] (ISPN-2757) ReplaceCommand in REPL mode cluster does not perform any modifications if the entry was not yet transfered during rehashing

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2757?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2757: -------------------------------- Summary: ReplaceCommand in REPL mode cluster does not perform any modifications if the entry was not yet transfered during rehashing (was: ReplaceCommand REPL mode cluster does not perform any modifications if the entry was not yet transfered during rehashing) > ReplaceCommand in REPL mode cluster does not perform any modifications if the entry was not yet transfered during rehashing > --------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2757 > URL: https://issues.jboss.org/browse/ISPN-2757 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta5 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 5.2.0.Final > > > The local data container does not have the entry yet so the ReplaceCommand fails. See BaseReplStateTransferConsistencyTest.testReplace(). -- 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
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2013