June 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1855) Accessing a non-distributed cache from a RemoteCacheManager can break topology updates

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-1855?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1855: ----------------------------------- Fix Version/s: 6.0.0.Final (was: 5.3.0.Final) > Accessing a non-distributed cache from a RemoteCacheManager can break topology updates > -------------------------------------------------------------------------------------- > > Key: ISPN-1855 > URL: https://issues.jboss.org/browse/ISPN-1855 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.1.1.FINAL > Reporter: Dan Berindei > Assignee: Galder Zamarreño > Fix For: 6.0.0.Final > > > RemoteCacheManager uses a single consistent hash to map requests to different servers, but caches on the server may have different CHs (or even no CH if the cache is not in distributed mode). > If the first request goes to a on-distributed cache, the client will never request an updated CH and so it will use a round robin strategy for routing request to all the caches. Obviously this is not optimal for distributed caches. > Each distributed cache can also have different members since 5.1, so it would be best if we kept a separate CH per cache on the client. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2669) Add a Active-Passive Failover Strategy for Hot Rod client

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2669?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-2669: ---------------------------------------- [~saturnism], is this JIRA still relevant given what [~gabriel_mircea] said? > Add a Active-Passive Failover Strategy for Hot Rod client > --------------------------------------------------------- > > Key: ISPN-2669 > URL: https://issues.jboss.org/browse/ISPN-2669 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Ray Tsang > Assignee: Galder Zamarreño > Fix For: 5.3.0.Final > > > Currently HotRod client has only Round Robin request balancing strategy. There may be use cases where user needs to do an active-passive setup where all requests to go primary active node and only fallback to passive node when active is down. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2836) org.jgroups.TimeoutException after invoking MapCombineCommand in Map/Reduce task with 2 nodes

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2836?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2836: -------------------------------- Assignee: Pedro Ruivo (was: Mircea Markus) > org.jgroups.TimeoutException after invoking MapCombineCommand in Map/Reduce task with 2 nodes > --------------------------------------------------------------------------------------------- > > Key: ISPN-2836 > URL: https://issues.jboss.org/browse/ISPN-2836 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.2.1.Final > Reporter: Alan Field > Assignee: Pedro Ruivo > Priority: Blocker > Labels: onboard > Fix For: 5.3.0.Final > > Attachments: afield-tcp-521-final.txt, udp-edg-perf01.txt, udp-edg-perf02.txt > > > Using RadarGun and two nodes to execute the example WordCount Map/Reduce job against a cache with ~550 keys with a value size of 1MB is producing a thread deadlock. The cache is distributed with transactions disabled. > TCP transport deadlocks without throwing an exception. Disabling the send queue and setting UNICAST2.conn_expiry_timeout=0 prevents the deadlock, but the job does not complete. The nodes send "are-you-alive" messages back and forth, and I have seen the following exception: > {noformat} > 11:44:29,970 ERROR [org.jgroups.protocols.TCP] (OOB-98,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (76 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.distexec.mapreduce.MapReduceTask.execute(MapReduceTask.java:352) > at org.radargun.cachewrappers.InfinispanMapReduceWrapper.executeMapReduceTask(InfinispanMapReduceWrapper.java:98) > at org.radargun.stages.MapReduceStage.executeOnSlave(MapReduceStage.java:74) > at org.radargun.Slave$2.run(Slave.java:103) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > 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:662) > Caused by: java.util.concurrent.ExecutionException: org.infinispan.CacheException: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at org.infinispan.distexec.mapreduce.MapReduceTask$TaskPart.get(MapReduceTask.java:832) > at org.infinispan.distexec.mapreduce.MapReduceTask.executeMapPhaseWithLocalReduction(MapReduceTask.java:477) > at org.infinispan.distexec.mapreduce.MapReduceTask.execute(MapReduceTask.java:350) > ... 9 more > Caused by: org.infinispan.CacheException: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at org.infinispan.util.Util.rewrapAsCacheException(Util.java:541) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:186) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:515) > 11:44:29,978 ERROR [org.jgroups.protocols.TCP] (Timer-3,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (60 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:175) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:197) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:254) > at org.infinispan.remoting.rpc.RpcManagerImpl.access$000(RpcManagerImpl.java:80) > at org.infinispan.remoting.rpc.RpcManagerImpl$1.call(RpcManagerImpl.java:288) > ... 5 more > Caused by: org.jgroups.TimeoutException: timeout sending message to edg-perf02-32536 > at org.jgroups.blocks.MessageDispatcher.sendMessage(MessageDispatcher.java:390) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.processSingleCall(CommandAwareRpcDispatcher.java:301) > 11:44:29,979 ERROR [org.jgroups.protocols.TCP] (Timer-4,default,edg-perf01-1907) failed sending message to edg-perf02-32536 (63 bytes): java.net.SocketException: Socket closed, cause: null > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:179) > ... 11 more > {noformat} > With UDP transport, both threads are deadlocked. I will attach thread dumps from runs using TCP and UDP transport. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3168) Use createClusteredCacheManager instead of createCacheManager for clustered caches

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3168?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3168: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1865 > Use createClusteredCacheManager instead of createCacheManager for clustered caches > ---------------------------------------------------------------------------------- > > Key: ISPN-3168 > URL: https://issues.jboss.org/browse/ISPN-3168 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 5.3.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 5.3.0.Final > > > The overloads of {{TestCacheManagerFactory.createCacheManager(...)}} using the new configuration don't call {{amendTransport(...)}}, so the created cache managers will all use the same port range, and join the same cluster. Tests that need to create clustered cache managers should use {{TestCacheManagerFactory.createClusteredCacheManager(...)}} instead. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3168) Use createClusteredCacheManager instead of createCacheManager for clustered caches

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3168?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3168: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use createClusteredCacheManager instead of createCacheManager for clustered caches > ---------------------------------------------------------------------------------- > > Key: ISPN-3168 > URL: https://issues.jboss.org/browse/ISPN-3168 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 5.3.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 5.3.0.Final > > > The overloads of {{TestCacheManagerFactory.createCacheManager(...)}} using the new configuration don't call {{amendTransport(...)}}, so the created cache managers will all use the same port range, and join the same cluster. Tests that need to create clustered cache managers should use {{TestCacheManagerFactory.createClusteredCacheManager(...)}} instead. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3058) HotRodTargetMigrator swallowing exceptions

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3058?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3058: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > HotRodTargetMigrator swallowing exceptions > ------------------------------------------ > > Key: ISPN-3058 > URL: https://issues.jboss.org/browse/ISPN-3058 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.5.Final, 5.3.0.Alpha1 > Reporter: Galder Zamarreño > Assignee: Tristan Tarrant > Fix For: 5.3.0.Final > > > {code} > try { > cache.get(key); > int i = count.getAndIncrement(); > if (log.isDebugEnabled() && i % 100 == 0) > log.debugf(">> Moved %s keys\n", i); > } catch (Exception e) { > }{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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3167) Upgrade JTA to Narayana 4.17.4

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-3167?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-3167: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade JTA to Narayana 4.17.4 > ------------------------------ > > Key: ISPN-3167 > URL: https://issues.jboss.org/browse/ISPN-3167 > Project: Infinispan > Issue Type: Component Upgrade > Components: Transactions > Affects Versions: 5.3.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 5.3.0.Final > > > To align with other components (i.e. EAP) -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3166) BackupReceiverRepositoryImpl generates NPE on cache shutdown

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/ISPN-3166?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz updated ISPN-3166: -------------------------------------- Status: Closed (was: Pull Request Sent) Fix Version/s: 5.3.0.Final Resolution: Done The issue has been fixed in 5.3.0-SNAPSHOT. > BackupReceiverRepositoryImpl generates NPE on cache shutdown > ------------------------------------------------------------ > > Key: ISPN-3166 > URL: https://issues.jboss.org/browse/ISPN-3166 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 5.3.0.Beta2, 5.3.0.CR1 > Reporter: Richard Achmatowicz > Assignee: Mircea Markus > Fix For: 5.3.0.Final > > > In the method BackupReceiverRepositoryImpl.getBackupCachemanager(), when creating a SiteCachePair for a cache with no explicitly configured backup, the localCacheName is not being set. This results in an NPE when shutting down the cache. > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3178) Fix CHMv8 bug with tree hash bins

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-3178: -------------------------------------- Summary: Fix CHMv8 bug with tree hash bins Key: ISPN-3178 URL: https://issues.jboss.org/browse/ISPN-3178 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.3.0.Final Verify that http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20130601/... fails with our CHMv8 and update it with the fix in http://gee.cs.oswego.edu/cgi-bin/viewcvs.cgi/jsr166/src/main/java/util/co... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3177) "Read past EOF" in case of using async fileStore with "infinispan" directory_provider

by Anna Manukyan (JIRA)

Anna Manukyan created ISPN-3177: ----------------------------------- Summary: "Read past EOF" in case of using async fileStore with "infinispan" directory_provider Key: ISPN-3177 URL: https://issues.jboss.org/browse/ISPN-3177 Project: Infinispan Issue Type: Bug Components: Lucene Directory, Querying Affects Versions: 5.2.4.Final Reporter: Anna Manukyan Assignee: Sanne Grinovero Attachments: config.xml The cache configuration is attached (config.xml). While trying to run performance tests on the cache configured in the provided XML, i.e. performing parallel puts/gets with many threads (local mode), the following exception is thrown: Please note that exception is thrown on Put. I've changed the tests so that only one thread is run, but anyway this issue appears. If I comment the loader's part, then the test passes. {code} org.hibernate.search.SearchException: HSEARCH000103: Unable to initialize IndexManager query at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManager(IndexManagerHolder.java:230) at org.hibernate.search.indexes.impl.IndexManagerHolder.buildEntityIndexBinding(IndexManagerHolder.java:102) at org.hibernate.search.spi.SearchFactoryBuilder.initDocumentBuilders(SearchFactoryBuilder.java:414) at org.hibernate.search.spi.SearchFactoryBuilder.buildIncrementalSearchFactory(SearchFactoryBuilder.java:169) at org.hibernate.search.spi.SearchFactoryBuilder.buildSearchFactory(SearchFactoryBuilder.java:149) at org.hibernate.search.impl.MutableSearchFactory.addClasses(MutableSearchFactory.java:194) at org.infinispan.query.backend.QueryInterceptor.enableClassesIncrementally(QueryInterceptor.java:225) at org.infinispan.query.backend.QueryInterceptor.updateKnownTypesIfNeeded(QueryInterceptor.java:250) at org.infinispan.query.backend.QueryInterceptor.processPutKeyValueCommand(QueryInterceptor.java:426) at org.infinispan.query.backend.QueryInterceptor.visitPutKeyValueCommand(QueryInterceptor.java:128) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) at org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor.visitPutKeyValueCommand(NonTransactionalLockingInterceptor.java:84) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:132) at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:62) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) at org.infi^Cnispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:128) at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:92) at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:62) at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:77) at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:343) at org.infinispan.CacheImpl.executeCommandAndCommitIfNeeded(CacheImpl.java:1162) at org.infinispan.CacheImpl.putInternal(CacheImpl.java:760) at org.infinispan.CacheImpl.put(CacheImpl.java:754) at org.infinispan.CacheImpl.put(CacheImpl.java:748) at org.infinispan.CacheSupport.put(CacheSupport.java:53) at org.radargun.cachewrappers.InfinispanWrapper.put(InfinispanWrapper.java:244) at org.radargun.cachewrappers.InfinispanExplicitLockingWrapper.put(InfinispanExplicitLockingWrapper.java:72) at org.radargun.cachewrappers.InfinispanQueryWrapper.put(InfinispanQueryWrapper.java:72) at org.radargun.stressors.StressTestStressor$FixedSetPerThreadOperationLogic.init(StressTestStressor.java:313) at org.radargun.stressors.StressTestStressor$Stressor.run(StressTestStressor.java:541) Caused by: org.hibernate.search.SearchException: Could not initialize index at org.hibernate.search.store.impl.DirectoryProviderHelper.initializeIndexIfNeeded(DirectoryProviderHelper.java:162) at org.hibernate.search.infinispan.impl.InfinispanDirectoryProvider.start(InfinispanDirectoryProvider.java:103) at org.hibernate.search.indexes.impl.DirectoryBasedIndexManager.initialize(DirectoryBasedIndexManager.java:104) at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManager(IndexManagerHolder.java:227) ... 33 more Caused by: java.io.IOException: Read past EOF at org.infinispan.lucene.SingleChunkIndexInput.readByte(SingleChunkIndexInput.java:77) at org.apache.lucene.store.ChecksumIndexInput.readByte(ChecksumIndexInput.java:41) at org.apache.lucene.store.DataInput.readInt(DataInput.java:86) at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:272) at org.apache.lucene.index.IndexFileDeleter.<init>(IndexFileDeleter.java:182) at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1168) at org.hibernate.search.store.impl.DirectoryProviderHelper.initializeIndexIfNeeded(DirectoryProviderHelper.java:157) ... 36 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2013