September 2017 - infinispan-issues

[JBoss JIRA] (ISPN-8306) InfinispanRegionFactory should use MemoryConfiguration

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-8306?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-8306: ------------------------------- Summary: InfinispanRegionFactory should use MemoryConfiguration (was: InfinispanRegionFactory still utilises Eviction) > InfinispanRegionFactory should use MemoryConfiguration > ------------------------------------------------------ > > Key: ISPN-8306 > URL: https://issues.jboss.org/browse/ISPN-8306 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8127) Prevent Hot Rod client from failing on certain scenarios

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8127?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-8127: ---------------------------------------- What scenarios? Please explain. > Prevent Hot Rod client from failing on certain scenarios > -------------------------------------------------------- > > Key: ISPN-8127 > URL: https://issues.jboss.org/browse/ISPN-8127 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud Integrations, Remote Protocols > Reporter: Sebastian Łaskawiec > > In some scenarios it should be possible to use Hot Rod client in graceful mode. It shouldn't fail when it can not contact the server (especially when {{putIfAbsent}} is concerned). > As long as near caching is concerned, we could provide stale data in such scenario. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8307) Add Store tests when using OffHeap

by William Burns (JIRA)

William Burns created ISPN-8307: ----------------------------------- Summary: Add Store tests when using OffHeap Key: ISPN-8307 URL: https://issues.jboss.org/browse/ISPN-8307 Project: Infinispan Issue Type: Task Components: Eviction, Loaders and Stores Reporter: William Burns We need to add some tests to make sure that off heap works properly when a store is used. Especially when passivation is enabled as that requires deeper support in the data container. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8111) OffHeapBoundedSingleNodeTest.testMultiThreaded fails with trace logging enabled

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8111?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8111: ------------------------------------- Oops forgot to change that, sorry :) > OffHeapBoundedSingleNodeTest.testMultiThreaded fails with trace logging enabled > ------------------------------------------------------------------------------- > > Key: ISPN-8111 > URL: https://issues.jboss.org/browse/ISPN-8111 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.1.0.Final > Reporter: Dan Berindei > Assignee: William Burns > Priority: Critical > Labels: testsuite_stability > > This is related to ISPN-8110, but it may be possible to fix ISPN-8110 and still have {{OffHeapBoundedSingleNodeTest.testMultiThreaded}} take more than 10 seconds. > 10 seconds seems more than enough for a CPU-bound test, but maybe we need to allow for more time when trace logging is enabled, or maybe we can test only the data container to eliminate the unrelated logging from the (unnecessary, I think) commands and interceptors: > {noformat} > 15:52:10,227 TRACE (testng-Test:[]) [InvocationContextInterceptor] Invoked with command PutKeyValueCommand{key=WrappedByteArray{bytes=[B0x010201046B657931, hashCode=1745974967}, value=WrappedByteArray{bytes=[B0x0102010676616C75..[10], hashCode=635645735}, flags=[], commandInvocationId=, putIfAbsent=false, valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=null}, successful=true, topologyId=-1} and InvocationContext [org.infinispan.context.impl.LocalTxInvocationContext@5f3c06c1] > 15:52:10,229 TRACE (testng-Test:[]) [InvocationContextInterceptor] Invoked with command PrepareCommand {modifications=[PutKeyValueCommand{key=WrappedByteArray{bytes=[B0x010201046B657931, hashCode=1745974967}, value=WrappedByteArray{bytes=[B0x0102010676616C75..[10], hashCode=635645735}, flags=[], commandInvocationId=, putIfAbsent=false, valueMatcher=MATCH_ALWAYS, metadata=EmbeddedExpirableMetadata{lifespan=-1, maxIdle=-1, version=null}, successful=true, topologyId=-1}], onePhaseCommit=false, retried=false, gtx=GlobalTx:local:2, cacheName='___defaultcache', topologyId=-1} and InvocationContext [org.infinispan.context.impl.LocalTxInvocationContext@3bc20a52] > 15:52:10,231 TRACE (testng-Test:[]) [InvocationContextInterceptor] Invoked with command CommitCommand {gtx=GlobalTx:local:2, cacheName='___defaultcache', topologyId=-1} and InvocationContext [org.infinispan.context.impl.LocalTxInvocationContext@2af56f39] > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7192) Replace RemoteCache.getRemoteCacheManager() with method that returns RemoteCacheContainer

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7192?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-7192: ------------------------------------- Assignee: Galder Zamarreño > Replace RemoteCache.getRemoteCacheManager() with method that returns RemoteCacheContainer > ----------------------------------------------------------------------------------------- > > Key: ISPN-7192 > URL: https://issues.jboss.org/browse/ISPN-7192 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 9.0.0.Alpha4 > Reporter: Paul Ferraro > Assignee: Galder Zamarreño > > org.infinispan.Cache already has a getCacheManager() method that returns an interface. Let's generalize this to BasicCache such that RemoteCache has an analogous method that returns RemoteCacheContainer. > However, the naming is really inconsistent. Should we name these: > BasicCache.getCacheManager()::BasicCacheContainer > Cache.getCacheManager()::EmbeddedCacheManager > RemoteCache.getCacheManager()::RemoteCacheContainer > or: > BasicCache.getCacheContainer()::BasicCacheContainer > Cache.getCacheContainer()::EmbeddedCacheManager > RemoteCache.getCacheContainer()::RemoteCacheContainer > It would be great if we could standardize the "cache manager" vs "cache container" naming convention. Given that "cache container" seems more prevalent in the API, I suggest going with that convention. This is complicated by the fact that org.infinispan.manager.CacheContainer already exists, but is not particularly useful. > 1. Creating a new org.infinispan.CacheContainer (in the same package as Cache, maybe extending org.infinispan.manager.CacheContainer) with some API refinements. e.g. getName()::String, getDefaultCacheName()::String, remove cruft, etc. > 2. Deprecate EmbeddedCacheManager and have it extend this new CacheContainer interface and deprecate it. > That way we can have: > BasicCache.getCacheContainer()::BasicCacheContainer > Cache.getCacheContainer()::org.infinispan.CacheContainer > RemoteCache.getCacheContainer()::RemoteCacheContainer -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3035) Members can re-appear by itself in the consistent hash after leaving

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3035?page=com.atlassian.jira.plugin.... ] Dan Berindei resolved ISPN-3035. -------------------------------- Fix Version/s: 9.0.0.Final Resolution: Out of Date Most likely fixed when we switched from UNICAST2 to UNICAST3. > Members can re-appear by itself in the consistent hash after leaving > -------------------------------------------------------------------- > > Key: ISPN-3035 > URL: https://issues.jboss.org/browse/ISPN-3035 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 5.2.5.Final, 5.3.0.Alpha1 > Reporter: Dan Berindei > Fix For: 9.0.0.Final > > Attachments: dret.log, dret2.log > > > Seen as an intermittent failure in DataRehashedEventTest: > {noformat} > 2013-04-23 14:07:45,459 DEBUG (testng-DataRehashedEventTest) [org.infinispan.manager.DefaultCacheManager] Stopping cache manager ISPN on NodeC-58711 > 2013-04-23 14:07:45,468 INFO (testng-DataRehashedEventTest) [org.infinispan.remoting.transport.jgroups.JGroupsTransport] ISPN000080: Disconnecting and closing JGroups Channel > 2013-04-23 14:07:46,469 DEBUG (testng-DataRehashedEventTest) [org.jgroups.protocols.pbcast.GMS] NodeC-58711: sending LEAVE request to NodeA-28008 > 2013-04-23 14:07:46,489 DEBUG (Incoming-2,ISPN,NodeA-28008) [org.jgroups.protocols.pbcast.GMS] NodeA-28008: installing [NodeA-28008|4] [NodeA-28008, NodeB-46156, NodeC-58711] > 2013-04-23 14:07:46,491 DEBUG (asyncTransportThread-0,NodeA) [org.infinispan.topology.ClusterTopologyManagerImpl] Starting cluster-wide rebalance for cache ___defaultcache, topology = CacheTopology{id=8, currentCH=DefaultConsistentHash{numSegments=60, numOwners=2, members=[NodeA-28008, NodeB-46156]}, pendingCH=DefaultConsistentHash{numSegments=60, numOwners=2, members=[NodeA-28008, NodeB-46156, NodeC-58711]}} > 2013-04-23 14:07:49,493 ERROR (testng-DataRehashedEventTest) [org.infinispan.test.fwk.UnitTestTestNGListener] Test testJoinAndLeave(org.infinispan.statetransfer.DataRehashedEventTest) failed. > java.lang.AssertionError: expected [2] but found [6] > at org.testng.Assert.fail(Assert.java:94) > at org.testng.Assert.failNotEquals(Assert.java:494) > at org.testng.Assert.assertEquals(Assert.java:123) > at org.testng.Assert.assertEquals(Assert.java:370) > at org.testng.Assert.assertEquals(Assert.java:380) > at org.infinispan.statetransfer.DataRehashedEventTest.testJoinAndLeave(DataRehashedEventTest.java:114) > {noformat} > The initial cluster has 3 nodes: A, B, C. C is killed, but somehow remains in the ClusterCacheStatus on the coordinator. > Then C re-appears in the JGroups view (possibly a JGroups issue). The problem in Infinispan is that the coordinator now sees C as a joiner, and it rebalances the cache to include C in the consistent hash again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8305) PessimisticTxPartitionAndMergeDuringPrepareTest.testPrimaryOwnerIsolatedPartitionWithDiscard[DIST_SYNC] randomly failing

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8305?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-8305: -------------------------------------- Assignee: Pedro Ruivo > PessimisticTxPartitionAndMergeDuringPrepareTest.testPrimaryOwnerIsolatedPartitionWithDiscard[DIST_SYNC] randomly failing > ------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-8305 > URL: https://issues.jboss.org/browse/ISPN-8305 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.0.Final > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Labels: testsuite_stability > > Dan said it could be related to ISPN-8232 (Dan had not seen failures since ISPN-6997) > {code} > Error Message > Expected key 'MagicKey#k1{151C/F56895B4/127@PessimisticTxPartitionAndMergeDuringPrepareTest[DIST_SYNC]-NodeB-47561}' to be locked on cache 'Cache 'pes-cache'@PessimisticTxPartitionAndMergeDuringPrepareTest[DIST_SYNC]-NodeB-47561' > Stacktrace > java.lang.AssertionError: Expected key 'MagicKey#k1{151C/F56895B4/127@PessimisticTxPartitionAndMergeDuringPrepareTest[DIST_SYNC]-NodeB-47561}' to be locked on cache 'Cache 'pes-cache'@PessimisticTxPartitionAndMergeDuringPrepareTest[DIST_SYNC]-NodeB-47561' > at org.infinispan.test.AbstractCacheTest.assertLocked(AbstractCacheTest.java:77) > at org.infinispan.partitionhandling.PessimisticTxPartitionAndMergeDuringPrepareTest.checkLocksDuringPartition(PessimisticTxPartitionAndMergeDuringPrepareTest.java:75) > at org.infinispan.partitionhandling.BasePessimisticTxPartitionAndMergeTest.doTest(BasePessimisticTxPartitionAndMergeTest.java:79) > at org.infinispan.partitionhandling.PessimisticTxPartitionAndMergeDuringPrepareTest.testPrimaryOwnerIsolatedPartitionWithDiscard(PessimisticTxPartitionAndMergeDuringPrepareTest.java:41) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > ... Removed 18 stack frames{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8305) PessimisticTxPartitionAndMergeDuringPrepareTest.testPrimaryOwnerIsolatedPartitionWithDiscard[DIST_SYNC] randomly failing

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8305?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8305: ----------------------------------- Affects Version/s: 9.1.0.Final > PessimisticTxPartitionAndMergeDuringPrepareTest.testPrimaryOwnerIsolatedPartitionWithDiscard[DIST_SYNC] randomly failing > ------------------------------------------------------------------------------------------------------------------------ > > Key: ISPN-8305 > URL: https://issues.jboss.org/browse/ISPN-8305 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.0.Final > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Labels: testsuite_stability > > Dan said it could be related to ISPN-8232 (Dan had not seen failures since ISPN-6997) > {code} > Error Message > Expected key 'MagicKey#k1{151C/F56895B4/127@PessimisticTxPartitionAndMergeDuringPrepareTest[DIST_SYNC]-NodeB-47561}' to be locked on cache 'Cache 'pes-cache'@PessimisticTxPartitionAndMergeDuringPrepareTest[DIST_SYNC]-NodeB-47561' > Stacktrace > java.lang.AssertionError: Expected key 'MagicKey#k1{151C/F56895B4/127@PessimisticTxPartitionAndMergeDuringPrepareTest[DIST_SYNC]-NodeB-47561}' to be locked on cache 'Cache 'pes-cache'@PessimisticTxPartitionAndMergeDuringPrepareTest[DIST_SYNC]-NodeB-47561' > at org.infinispan.test.AbstractCacheTest.assertLocked(AbstractCacheTest.java:77) > at org.infinispan.partitionhandling.PessimisticTxPartitionAndMergeDuringPrepareTest.checkLocksDuringPartition(PessimisticTxPartitionAndMergeDuringPrepareTest.java:75) > at org.infinispan.partitionhandling.BasePessimisticTxPartitionAndMergeTest.doTest(BasePessimisticTxPartitionAndMergeTest.java:79) > at org.infinispan.partitionhandling.PessimisticTxPartitionAndMergeDuringPrepareTest.testPrimaryOwnerIsolatedPartitionWithDiscard(PessimisticTxPartitionAndMergeDuringPrepareTest.java:41) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > ... Removed 18 stack frames{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8306) InfinispanRegionFactory still utilises Eviction

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-8306: ---------------------------------- Summary: InfinispanRegionFactory still utilises Eviction Key: ISPN-8306 URL: https://issues.jboss.org/browse/ISPN-8306 Project: Infinispan Issue Type: Bug Components: Hibernate Cache Affects Versions: 9.1.0.Final Reporter: Ryan Emerson Assignee: Ryan Emerson -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8305) PessimisticTxPartitionAndMergeDuringPrepareTest.testPrimaryOwnerIsolatedPartitionWithDiscard[DIST_SYNC] randomly failing

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-8305: -------------------------------------- Summary: PessimisticTxPartitionAndMergeDuringPrepareTest.testPrimaryOwnerIsolatedPartitionWithDiscard[DIST_SYNC] randomly failing Key: ISPN-8305 URL: https://issues.jboss.org/browse/ISPN-8305 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Dan said it could be related to ISPN-8232 (Dan had not seen failures since ISPN-6997) {code} testPrimaryOwnerIsolatedPartitionWithDiscard[DIST_SYNC] java.lang.AssertionError: Expected key 'MagicKey#k1{151C/F56895B4/127@PessimisticTxPartitionAndMergeDuringPrepareTest[DIST_SYNC]-NodeB-47561}' to be locked on cache 'Cache 'pes-cache'@PessimisticTxPartitionAndMergeDuringPrepareTest[DIST_SYNC]-NodeB-47561' at org.infinispan.test.AbstractCacheTest.assertLocked(AbstractCacheTest.java:77) at org.infinispan.partitionhandling.PessimisticTxPartitionAndMergeDuringPrepareTest.checkLocksDuringPartition(PessimisticTxPartitionAndMergeDuringPrepareTest.java:75) at org.infinispan.partitionhandling.BasePessimisticTxPartitionAndMergeTest.doTest(BasePessimisticTxPartitionAndMergeTest.java:79) at org.infinispan.partitionhandling.PessimisticTxPartitionAndMergeDuringPrepareTest.testPrimaryOwnerIsolatedPartitionWithDiscard(PessimisticTxPartitionAndMergeDuringPrepareTest.java:41) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ... Removed 18 stack frames {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 September 2017