April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5022) Create a cachestore archetype

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5022?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5022: ------------------------------------ Fix Version/s: 7.2.0.Final (was: 7.2.0.CR1) > Create a cachestore archetype > ----------------------------- > > Key: ISPN-5022 > URL: https://issues.jboss.org/browse/ISPN-5022 > Project: Infinispan > Issue Type: Feature Request > Components: Demos and Tutorials, Loaders and Stores > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.2.0.Final > > > We should have an AdvancedCacheWriter archetype which describes how to implement a proper cache store. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5073) Improve "Number of Entries" stats

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5073?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5073: ------------------------------------ Fix Version/s: 7.2.0.Final (was: 7.2.0.CR1) > Improve "Number of Entries" stats > --------------------------------- > > Key: ISPN-5073 > URL: https://issues.jboss.org/browse/ISPN-5073 > Project: Infinispan > Issue Type: Task > Components: Core, JMX, reporting and management > Affects Versions: 7.1.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Vladimir Blagojevic > Fix For: 7.2.0.Final > > > Currently the getNumberOfEntries in CacheMgmtInterceptor returns the size of the datacontainer which doesn't take into account expired entries and cache stores. > To avoid compatibility issues, modify the description to reflect its behaviour and add proper statistics, possibly with different flag combinations (SKIP_REMOTE, SKIP_CACHE_LOAD) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5067) CLI for server docs need updating to reflect WildFly base

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5067?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5067: ------------------------------------ Fix Version/s: 7.2.0.Final (was: 7.2.0.CR1) > CLI for server docs need updating to reflect WildFly base > --------------------------------------------------------- > > Key: ISPN-5067 > URL: https://issues.jboss.org/browse/ISPN-5067 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Servers > Affects Versions: 7.1.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5046) PartitionHandling: split during commit can leave the cache inconsistent after merge

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5046?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5046: ------------------------------------ Fix Version/s: 7.2.0.Final (was: 7.2.0.CR1) > PartitionHandling: split during commit can leave the cache inconsistent after merge > ----------------------------------------------------------------------------------- > > Key: ISPN-5046 > URL: https://issues.jboss.org/browse/ISPN-5046 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.2.Final, 7.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 7.2.0.Final > > > Say we have a cluster ABCD; a transaction T was started on A, with B as the primary owner and C the backup owner. B and C both acknowledge the prepare, and the network splits into AB and CD right before A sends the commit command. Eventually A suspects C and D, but the commit still succeeds on B before C and D are suspected. And SuspectExceptions are ignored for commit commands, so the user won't see any error. > However, C will eventually suspect A and B. When the CD cache topology is installed, it will roll back transaction T. After the merge, both partitions are in degraded mode, so we assume that they both have the latest data and the key is never updated on C. > From C's point of view, this is very similar to ISPN-3421. The fix should also be similar, we could delay the transaction rollback on C until we get a confirmation from B that T was not committed there. Since B is inaccessible, it will eventually get a SuspectException and the CD cache topology, at which point the cache is in degraded mode and it can wait for a merge. On merge, it should check the status of the transaction on B again, and either commit or rollback based on what B did. > We also need to suspend the cleanup of completed transactions while the cache is in degraded mode, otherwise C might not find T on B after the merge. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5192) infinispan-remote uber jar contains 2x versions of shaded javassist packages

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5192?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5192: ------------------------------------ Fix Version/s: 7.2.0.Final (was: 7.2.0.CR1) > infinispan-remote uber jar contains 2x versions of shaded javassist packages > ----------------------------------------------------------------------------- > > Key: ISPN-5192 > URL: https://issues.jboss.org/browse/ISPN-5192 > Project: Infinispan > Issue Type: Bug > Components: Build process, Remote Protocols > Affects Versions: 7.1.0.CR2 > Reporter: Tristan Tarrant > Assignee: Adrian Nistor > Fix For: 7.2.0.Final > > > Both the shaded protostream library and the infinispan-remote uberjar package javassist. The latter should be removed. The package should be relocated to avoid conflict with containers which expose the library (i.e. weblogic) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5151) DistributedSharedCacheTwoNodesMapReduceTest.testInvokeMapReduceOnAllKeys random failures

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5151?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5151: ------------------------------------ Fix Version/s: 7.2.0.Final (was: 7.2.0.CR1) > DistributedSharedCacheTwoNodesMapReduceTest.testInvokeMapReduceOnAllKeys random failures > ---------------------------------------------------------------------------------------- > > Key: ISPN-5151 > URL: https://issues.jboss.org/browse/ISPN-5151 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite - Core > Affects Versions: 7.0.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 7.2.0.Final > > > The method {{invokeMapReduce()}} doesn't really invoke the M/R task, it only creates it, and the execution only starts when the test method calls {{task.execute()}} explicitly. It shouldn't try to check the contents of the shared intermediary cache, because the intermediary cache may not exist yet - and it may accidentally create it with the wrong configuration. I get this error when I run only the {{testInvokeMapReduceOnAllKeys}} method: > {noformat} > 09:55:37,632 TRACE (testng-DistributedSharedCacheTwoNodesMapReduceTest:) [DefaultCacheManager] About to wire and start cache __tmpMapReduce > 09:55:37,646 DEBUG (testng-DistributedSharedCacheTwoNodesMapReduceTest:) [MapReduceTask] Invoking CreateCacheCommand{cacheManager=null, cacheNameToCreate='__tmpMapReduce', cacheConfigurationName='__tmpMapReduce', start=true', size=2} across members [DistributedSharedCacheTwoNodesMapReduceTest-NodeA-19271, DistributedSharedCacheTwoNodesMapReduceTest-NodeB-10341] > 10:32:56,324 ERROR (testng-DistributedSharedCacheTwoNodesMapReduceTest:) [UnitTestTestNGListener] Test testInvokeMapReduceOnAllKeys(org.infinispan.distexec.mapreduce.DistributedSharedCacheTwoNodesMapReduceTest) failed. > org.infinispan.distexec.mapreduce.MapReduceException: Map phase failed > at org.infinispan.distexec.mapreduce.MapReduceTask.executeMapPhase(MapReduceTask.java:607) > at org.infinispan.distexec.mapreduce.MapReduceTask.executeHelper(MapReduceTask.java:473) > at org.infinispan.distexec.mapreduce.MapReduceTask.execute(MapReduceTask.java:414) > at org.infinispan.distexec.mapreduce.BaseWordCountMapReduceTest.testInvokeMapReduceOnAllKeys(BaseWordCountMapReduceTest.java:162) > Caused by: org.infinispan.commons.CacheException: java.lang.NullPointerException > at org.infinispan.distexec.mapreduce.MapReduceManagerImpl.mapAndCombineForDistributedReduction(MapReduceManagerImpl.java:105) > at org.infinispan.distexec.mapreduce.MapReduceTask$MapTaskPart.invokeMapCombineLocally(MapReduceTask.java:1174) > at org.infinispan.distexec.mapreduce.MapReduceTask$MapTaskPart.access$300(MapReduceTask.java:1101) > at org.infinispan.distexec.mapreduce.MapReduceTask$MapTaskPart$1.call(MapReduceTask.java:1123) > at org.infinispan.distexec.mapreduce.MapReduceTask$MapTaskPart$1.call(MapReduceTask.java:1119) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at org.infinispan.distexec.mapreduce.MapReduceManagerImpl.mapKeysToNodes(MapReduceManagerImpl.java:363) > at org.infinispan.distexec.mapreduce.MapReduceManagerImpl.migrateIntermediateKeysAndValues(MapReduceManagerImpl.java:327) > at org.infinispan.distexec.mapreduce.MapReduceManagerImpl.mapAndCombine(MapReduceManagerImpl.java:260) > at org.infinispan.distexec.mapreduce.MapReduceManagerImpl.mapAndCombineForDistributedReduction(MapReduceManagerImpl.java:103) > ... 10 more > {noformat} > Even if the check is moved after the M/R task is finished, it still wouldn't be correct, because the task only cleans up the shared intermediary cache asynchronously. So it needs to use {{eventually()}} to avoid errors like this: > {noformat} > 04:06:32,260 ERROR (testng-DistributedSharedCacheTwoNodesMapReduceTest:) [UnitTestTestNGListener] Test testInvokeMapReduceOnAllKeys(org.infinispan.distexec.mapreduce.DistributedSharedCacheTwoNodesMapReduceTest) failed. > java.lang.AssertionError: Shared cache __tmpMapReduce is not empty. It has 5 keys/values: [ImmortalCacheEntry{key=IntermediateCompositeKey [taskId=88948a8b-2a8a-4c13-bc45-4dc3a9f6b0fb, key=is], value=org.infinispan.distexec.mapreduce.MapReduceManagerImpl$DeltaAwareList@21ae10d3}, ImmortalCacheEntry{key=IntermediateCompositeKey [taskId=88948a8b-2a8a-4c13-bc45-4dc3a9f6b0fb, key=JUDCon], value=org.infinispan.distexec.mapreduce.MapReduceManagerImpl$DeltaAwareList@108d6b51}, ImmortalCacheEntry{key=IntermediateCompositeKey [taskId=88948a8b-2a8a-4c13-bc45-4dc3a9f6b0fb, key=cool], value=org.infinispan.distexec.mapreduce.MapReduceManagerImpl$DeltaAwareList@77949e8f}, ImmortalCacheEntry{key=IntermediateCompositeKey [taskId=88948a8b-2a8a-4c13-bc45-4dc3a9f6b0fb, key=Infinispan], value=org.infinispan.distexec.mapreduce.MapReduceManagerImpl$DeltaAwareList@712a6071}, ImmortalCacheEntry{key=IntermediateCompositeKey [taskId=88948a8b-2a8a-4c13-bc45-4dc3a9f6b0fb, key=community], value=org.infinispan.distexec.mapreduce.MapReduceManagerImpl$DeltaAwareList@291bdf76}] expected:<0> but was:<5> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.infinispan.distexec.mapreduce.DistributedSharedCacheTwoNodesMapReduceTest.invokeMapReduce(DistributedSharedCacheTwoNodesMapReduceTest.java:44) > at org.infinispan.distexec.mapreduce.BaseWordCountMapReduceTest.testInvokeMapReduceOnAllKeys(BaseWordCountMapReduceTest.java:161) > 04:06:32,579 TRACE (transport-thread-NodeA-p29577-t6:) [InvocationContextInterceptor] Invoked with command RemoveCommand{key=IntermediateCompositeKey [taskId=eb7da48a-5922-4671-9037-4077e209744c, key=RedHat], value=null, flags=null, valueMatcher=MATCH_ALWAYS} and InvocationContext [org.infinispan.context.SingleKeyNonTxInvocationContext@c0bbc61] > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5163) A write operation with the SKIP_LOCKING flag can roll back the transaction

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5163?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5163: ------------------------------------ Fix Version/s: 7.2.0.Final (was: 7.2.0.CR1) > A write operation with the SKIP_LOCKING flag can roll back the transaction > -------------------------------------------------------------------------- > > Key: ISPN-5163 > URL: https://issues.jboss.org/browse/ISPN-5163 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.3.Final, 7.1.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.2.0.Final > > > When a write operation has the SKIP_LOCKING flag, it does not send a {{LockControlCommand}} to the primary owner, but it can send a {{ClusteredGetCommand}} with {{acquireRemoteLocks=true}} instead. The {{ClusteredGetCommmand}} will then execute a {{LockControlCommand}} with the origin not set properly, and {{TxInterceptor}} will roll back the transaction because the originator ({{null}}) appears to have left the cluster. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5093) Granularity of remote event listener implementations doing the same job

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5093?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5093: ------------------------------------ Fix Version/s: 7.2.0.Final (was: 7.2.0.CR1) > Granularity of remote event listener implementations doing the same job > ----------------------------------------------------------------------- > > Key: ISPN-5093 > URL: https://issues.jboss.org/browse/ISPN-5093 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.2.0.Final > > > Currently, if N clients add the same listener to a cache that does the same job, e.g. keeping a near cache consistent, this results in N server-side cluster listeners created, each potentially installed in different nodes. If one of those nodes fails, all clients that had a listener registered to that node will have to find a different node for this listener. > The downsides of this approach is that there are as many cluster listeners installed as clients have added listeners (or have near cache enabled), which might not very efficient. If a node goes down, all clients that have cluster listeners there need to failover to some other node. > The advantage of this approach is simplicity of the approach to decide where to add the listener and where to failover to. > For this type of scenarios, an alternative set up might be worth exploring: > If all these client side listeners are interested in exactly the same events, and the client ID would be exposed via the RemoteCache API, a server side cluster listener multi-plexing between all these clients could be potentially built. In other words, instead of having N clients register N cluster listeners, the first client would register the cluster listener with a client listener ID, and if more registrations were added with the same client listener ID, the connections would be added to the existing cluster listener implementation. > The maximise the efficiency of this solution, all clients (even running in different JMVs), given the same client listener ID, should agree upon the node to add the listener in. For a distributed cache, hashing on the cache name would work. For replicated caches, since there's no hashing available, the first node of the view could be used. > Since the logic to be executed server-side varies between being the first node adding the client listener vs the others, synchronization would be added to make sure that the first invocation only creates the cluster listener, and the others simply add the channel to the listener. > Failover is a bit more tricky too, because if the node with the cluster listener goes down, all the clients have to failover, which again exposes a 1st vs the others type of logic. > Advantages of this approach is the reduction in number of cluster listeners and potentially efficiency coming from a single cluster listener implementation server side. > The disadvantages come from the server side logic to add/failover a cluster listener, which need to take into account if the listener is present or not. Other disadvantages come from needing the clients to use some specific routing for adding listeners for same node. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5076) Pessimistic transactions can lose their locks when the primary owner changes

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5076?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5076: ------------------------------------ Fix Version/s: 7.2.0.Final (was: 7.2.0.CR1) > Pessimistic transactions can lose their locks when the primary owner changes > ---------------------------------------------------------------------------- > > Key: ISPN-5076 > URL: https://issues.jboss.org/browse/ISPN-5076 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.2.Final, 7.1.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: 7.0 > Fix For: 7.2.0.Final > > > In a pessimistic cache, if a transaction {{T1}} has a {{put(k, v)}} operation and the primary owner of the key is the originator, the lock is acquired on the originator but it is not replicated to on the backup(s). > If one of the backup owners becomes the primary owner, it will allow another transaction {{T2}} to lock (and update) key {{k}} before it receives the one-phase prepare command from the originator of {{T1}}. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5367) Cache putMap/getAll usage of SegmentAwareMap/Set performance investigation

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5367?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-5367: ------------------------------------ Fix Version/s: 7.2.0.Final (was: 7.2.0.CR1) > Cache putMap/getAll usage of SegmentAwareMap/Set performance investigation > -------------------------------------------------------------------------- > > Key: ISPN-5367 > URL: https://issues.jboss.org/browse/ISPN-5367 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 7.2.0.Final > > > With the putAll method I introduced a SegmentAwareMap and SegmentAwareSet in thoughts that not copying all the elements would help performance. Thinking more it may be better to just make a new shallow copy map for each target instead. Need to do some testing to make sure if one is clearly better than the other. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 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 April 2015