January 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2581) StateTransferManagerImpl.waitForInitialStateTransferToComplete() returns too soon

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2581?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2581: -------------------------------- Priority: Major (was: Critical) > StateTransferManagerImpl.waitForInitialStateTransferToComplete() returns too soon > --------------------------------------------------------------------------------- > > Key: ISPN-2581 > URL: https://issues.jboss.org/browse/ISPN-2581 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta5 > Reporter: Dan Berindei > Assignee: Adrian Nistor > Fix For: 5.2.0.Final > > > StateTransferManagerImpl.waitForInitialStateTransferToComplete() returns as soon as a joining node confirmed to the coordinator that it received all the data it needed (see STMI.notifyEndOfTopologyUpdate()). > It should return only after the coordinator has confirmed the end of the rebalance with a new topology update (see STMI.doTopologyUpdate()). > This should make it more likely for the tests suite clusters to be in a stable state by the time the test starts, and should help with the random state transfer-related failures in non-state transfer tests. > Instead we should make sure that we do have tests that check forwarding behaviour explicitly. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2575) KeyTransformer registration is required on all nodes of the cluster, in case of custom keys

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2575: -------------------------------- Fix Version/s: 5.3.0.Final (was: 5.2.0.Final) > KeyTransformer registration is required on all nodes of the cluster, in case of custom keys > ------------------------------------------------------------------------------------------- > > Key: ISPN-2575 > URL: https://issues.jboss.org/browse/ISPN-2575 > Project: Infinispan > Issue Type: Feature Request > Components: Querying > Affects Versions: 5.2.0.Beta5 > Reporter: Anna Manukyan > Assignee: Sanne Grinovero > Fix For: 5.3.0.Final > > Attachments: ClusteredCacheTest.java > > > The case is the following: > I have a clustered cache on which I want to perform a search. I'm doing the following: > I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception: > java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer > When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager. > The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer() -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2657) Support for LevelDB CacheStore

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2657?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2657: ------------------------------------- Level DB doesn't seem to support bulk load which makes preloading impossible. http://code.google.com/p/leveldb/ > Support for LevelDB CacheStore > ------------------------------ > > Key: ISPN-2657 > URL: https://issues.jboss.org/browse/ISPN-2657 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Ray Tsang > Assignee: Mircea Markus > Fix For: 7.0.0.Final > > > Support for LevelDB, a fast key-value persistence storage. > There is a pure java implementation and a jni by fuse -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2657) Support for LevelDB CacheStore

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2657?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2657: -------------------------------- Fix Version/s: 7.0.0.Final > Support for LevelDB CacheStore > ------------------------------ > > Key: ISPN-2657 > URL: https://issues.jboss.org/browse/ISPN-2657 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Ray Tsang > Assignee: Mircea Markus > Fix For: 7.0.0.Final > > > Support for LevelDB, a fast key-value persistence storage. > There is a pure java implementation and a jni by fuse -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2661) Not a mapped entity (don't forget to add @Indexed) is thrown in case of using Clustered Query

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2661?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2661: -------------------------------- Fix Version/s: 5.3.0.Final > Not a mapped entity (don't forget to add @Indexed) is thrown in case of using Clustered Query > --------------------------------------------------------------------------------------------- > > Key: ISPN-2661 > URL: https://issues.jboss.org/browse/ISPN-2661 > Project: Infinispan > Issue Type: Bug > Components: Querying > Reporter: Anna Manukyan > Assignee: Sanne Grinovero > Fix For: 5.3.0.Final > > Attachments: ClusteredQueryMassIndexingTest.java, DistributedMassIndexingTest.java > > > Running ClusteredQuery on Infinispan Distributed cache, throws the following exception: > {code} > org.infinispan.CacheException: org.hibernate.search.SearchException: Not a mapped entity (don't forget to add @Indexed): class org.infinispan.query.queries.faceting.Car > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:189) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:206) > at org.infinispan.query.clustered.ClusteredQueryInvoker.broadcast(ClusteredQueryInvoker.java:113) > at org.infinispan.query.clustered.ClusteredCacheQueryImpl.getResultSize(ClusteredCacheQueryImpl.java:96) > at org.infinispan.query.distributed.ClusteredQueryMassIndexingTest.verifyFindsCar(ClusteredQueryMassIndexingTest.java:26) > at org.infinispan.query.distributed.DistributedMassIndexingTest.verifyFindsCar(DistributedMassIndexingTest.java:105) > at org.infinispan.query.distributed.DistributedMassIndexingTest.testReindexing(DistributedMassIndexingTest.java:68) > 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) > Caused by: org.hibernate.search.SearchException: Not a mapped entity (don't forget to add @Indexed): class org.infinispan.query.queries.faceting.Car > at org.hibernate.search.query.engine.impl.HSQueryImpl.buildSearcher(HSQueryImpl.java:567) > at org.hibernate.search.query.engine.impl.HSQueryImpl.buildSearcher(HSQueryImpl.java:511) > at org.hibernate.search.query.engine.impl.HSQueryImpl.queryDocumentExtractor(HSQueryImpl.java:304) > at org.infinispan.query.clustered.commandworkers.CQGetResultSize.perform(CQGetResultSize.java:40) > at org.infinispan.query.clustered.ClusteredQueryCommand.perform(ClusteredQueryCommand.java:132) > at org.infinispan.query.clustered.ClusteredQueryCommand.perform(ClusteredQueryCommand.java:127) > at org.infinispan.remoting.InboundInvocationHandlerImpl.handleInternal(InboundInvocationHandlerImpl.java:101) > at org.infinispan.remoting.InboundInvocationHandlerImpl.handleWithWaitForBlocks(InboundInvocationHandlerImpl.java:122) > at org.infinispan.remoting.InboundInvocationHandlerImpl.handle(InboundInvocationHandlerImpl.java:86) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.executeCommandFromLocalCluster(CommandAwareRpcDispatcher.java:245) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.handle(CommandAwareRpcDispatcher.java:218) > at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:483) > at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:390) > at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:248) > at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:598) > at org.jgroups.JChannel.up(JChannel.java:703) > at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1020) > at org.jgroups.protocols.FRAG2.up(FRAG2.java:181) > at org.jgroups.protocols.FC.up(FC.java:479) > at org.jgroups.protocols.pbcast.GMS.up(GMS.java:896) > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:244) > at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:432) > at org.jgroups.protocols.pbcast.NAKACK2.handleMessage(NAKACK2.java:721) > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:574) > at org.jgroups.protocols.Discovery.up(Discovery.java:359) > at org.jgroups.protocols.TP.passMessageUp(TP.java:1287) > at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1850) > at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1823) > ... 3 more > {code} > Maybe this issue is related to ISPN-1568, but here my nodes are started properly and the test waits for the cluster to form properly. > You can find the test attached - ClusteredQueryMassIndexingTest.java which extends the DistributedMassIndexingTest (already from the testsuite). I've marked the verifyFindsCar() method there as protected for being able to override it. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2632) Uneven request balancing after node crash

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2632?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2632: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 886549|https://bugzilla.redhat.com/show_bug.cgi?id=886549] from MODIFIED to ON_QA > Uneven request balancing after node crash > ----------------------------------------- > > Key: ISPN-2632 > URL: https://issues.jboss.org/browse/ISPN-2632 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR1 > Reporter: Michal Linhard > Assignee: Galder Zamarreño > Priority: Blocker > Fix For: 5.2.0.CR2, 5.2.0.Final > > > This is a new manifestation of ISPN-1995, but in this case this happens after killing only one node: the hot rod requests aren't very well balanced. > these runs still manifest also ISPN-2550 and it may be cause of this bug. > The uneven balancing of requests can be seen here: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1954) Wrong ServerWorker thread name in Hot rod server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-1954?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-1954: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 745865|https://bugzilla.redhat.com/show_bug.cgi?id=745865] from MODIFIED to ON_QA > Wrong ServerWorker thread name in Hot rod server > ------------------------------------------------ > > Key: ISPN-1954 > URL: https://issues.jboss.org/browse/ISPN-1954 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.1.3.CR1 > Reporter: Michal Linhard > Assignee: Norman Maurer > Priority: Minor > Fix For: 5.2.0.CR1, 5.2.0.Final > > > When debugging/profiling JDG, we're seeing HotRod server calls being executed by MemcachedServerWorker threads. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2658) org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2658?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2658: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 888693|https://bugzilla.redhat.com/show_bug.cgi?id=888693] from MODIFIED to ON_QA > org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments > ------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-2658 > URL: https://issues.jboss.org/browse/ISPN-2658 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta6 > Reporter: Anna Manukyan > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 5.2.0.CR1 > > Attachments: testModificationsOnSameCustomKey-2.log > > > org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey test fails on all environments (RHEL, Windows, Solaris - JDK7, Open JDK7, IBM JDK7). > The error message is: > {code} > Error Message > Serialization count: expected 4 but was 5 > Stacktrace > java.lang.AssertionError: Serialization count: expected 4 but was 5 > at org.infinispan.marshall.MarshalledValueTest.assertSerializationCounts(MarshalledValueTest.java:135) > at org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey(MarshalledValueTest.java:452) > 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2580) Do not request segments from all nodes at once

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2580?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2580: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 881070|https://bugzilla.redhat.com/show_bug.cgi?id=881070] from MODIFIED to ON_QA > Do not request segments from all nodes at once > ---------------------------------------------- > > Key: ISPN-2580 > URL: https://issues.jboss.org/browse/ISPN-2580 > Project: Infinispan > Issue Type: Enhancement > Components: State transfer > Affects Versions: 5.2.0.Beta5 > Reporter: Radim Vansa > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 5.2.0.CR1 > > > When a new node joins large cluster filled with data, it gets the new CH and REBALANCE_START command, and requests data from all nodes at once (or almost all with even distribution of segments). It may be not able to handle this amount of transfers in parallel even at the JGroups level - this results in data sent to the node and discarded at the receiver, sent again and again. With a heavy congestion the node just buffers fragments of a message from one sender and never passes this up. > The number of StateRequestCommands(START_STATE_TRANSFER) should be limited so that the node is not congested. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2624) JDG: Storage-only example: HotRodDecoder: NSEE: key not found: node1/clustered

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2624?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2624: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 875151|https://bugzilla.redhat.com/show_bug.cgi?id=875151] from MODIFIED to ON_QA > JDG: Storage-only example: HotRodDecoder: NSEE: key not found: node1/clustered > ------------------------------------------------------------------------------ > > Key: ISPN-2624 > URL: https://issues.jboss.org/browse/ISPN-2624 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Reporter: Tomas Sykora > Assignee: Galder Zamarreño > Fix For: 5.2.0.CR1 > > Attachments: standalone-ha.xml, standalone-storage-only.xml, storageOnlyTraceMainNode.txt, storageOnlyTraceStorageOnlyNode.txt > > > This is issue to distinguish from https://issues.jboss.org/browse/ISPN-2550. > For logs and more info see related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=875151 > This issue was found during running JDG functional test suite for configuration examples provided with JDG. -- 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

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2013