March 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4546) Possible stale lock when the primary owner leaves during rebalance

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4546?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4546: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Possible stale lock when the primary owner leaves during rebalance > ------------------------------------------------------------------ > > Key: ISPN-4546 > URL: https://issues.jboss.org/browse/ISPN-4546 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.0.Alpha5 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.2.0.CR1 > > > Topology T: coordinator = A, owners(k) = [C, D], pending_owners(k) = null > B sends prepareCommand(tx1, put(k, v)) to C, D > D adds backup locks and replies > C acquires lock, ready to send reply to B > A starts installing topology T+1: owners(k) = [C, D], pending_owners(k) = [C, E] > A, C and E install topology T+1, B and D do not > E requests and receives tx data from C, including tx1 > C leaves > B sees a SuspectException, sends rollbackCommand(tx1) to C, D > D removes tx1 > C has left, but is ignored > B reports to the user that the tx has been rolled back > B and D install topology T+1 (optional) > A starts installing topology T+2: owners(k) = [D], pending_owners(k) = [E] > A, B, D, E all install topology T+2 > E requests and receives state from D, but it does not remove tx1 > A starts installing topology T+3: owners(k) = [E], pending_owners(k) = null > E now has a stale backup lock on k > It seems very hard to reproduce in production: C would have to leave soon enough so that B and D haven't received the T+1 topology yet, but late enough for it to send its transaction data to E. > A possible solution would be to catch any SuspectException during prepare/commit/rollback (without ignoring leavers), wait for a new topology, and replicate the command again on the new owners. Obviously, this wouldn't work with asynchronous prepare/commit/rollback. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4596) Avoid index cleanup operations on putIfAbsent

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4596?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4596: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Avoid index cleanup operations on putIfAbsent > --------------------------------------------- > > Key: ISPN-4596 > URL: https://issues.jboss.org/browse/ISPN-4596 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 7.2.0.CR1 > > > when doing a putIfAbsent() operation we can relax some of the internal cleanup operations, such as automatically enabling the Flag.SKIP_INDEX_CLEANUP -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4735) Remove TODOs from the documentation

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4735?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4735: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Remove TODOs from the documentation > ----------------------------------- > > Key: ISPN-4735 > URL: https://issues.jboss.org/browse/ISPN-4735 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core, Documentation-Query, Documentation-Servers > Reporter: Mircea Markus > Fix For: 7.2.0.CR1 > > > ATM the documentation has 38 todos, some of them being empty chapter in User Guide - pretty annoying for a new user trying to get used to Infinispan. Let's fixe all of these before 7.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4722) CLI remove is not cluster-wide

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4722?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4722: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > CLI remove is not cluster-wide > ------------------------------ > > Key: ISPN-4722 > URL: https://issues.jboss.org/browse/ISPN-4722 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 6.0.2.Final, 7.0.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Tristan Tarrant > Fix For: 7.2.0.CR1 > > > In CLI, the "remove" command does not delete entries in all nodes of a clustered environment, only the local copy. However, the "put" command does write in all nodes. Is it the expected behavior? See example below: > {code} > node 1 > put k1 v1 > get k1 -> v1 > node 2 > get k1 -> v1 > node 1 > remove k1 > get k1 -> null > node 2 > get k1 -> v1 > {code} > I know that these commands provided by CLI are not used in real world, but they are useful to demonstrate the correct configuration of a JDG cluster. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4624) Allow custom partition handling strategy

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4624?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4624: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Allow custom partition handling strategy > ---------------------------------------- > > Key: ISPN-4624 > URL: https://issues.jboss.org/browse/ISPN-4624 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 7.0.0.Beta1 > Reporter: Dan Berindei > Labels: partition_handling > Fix For: 7.2.0.CR1 > > > Users should be able to configure a custom PartitionHandlingStrategy. It should be able to specify a behaviour on merge as well. > We might want to merge this with the RebalancePolicy, which was also supposed to be configurable. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4824) Add complete-timeout and reaper-interval in the server transactions configuration

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4824?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4824: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Add complete-timeout and reaper-interval in the server transactions configuration > --------------------------------------------------------------------------------- > > Key: ISPN-4824 > URL: https://issues.jboss.org/browse/ISPN-4824 > Project: Infinispan > Issue Type: Task > Components: Configuration, Server > Affects Versions: 7.0.0.CR1 > Reporter: Dan Berindei > Fix For: 7.2.0.CR1 > > > We should allow server users to configure the time after which completed remote txs are cleaned up and how often the cleanup task runs. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4817) Cluster Listener replication of listener to remote dist nodes needs privilege action

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4817?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4817: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Cluster Listener replication of listener to remote dist nodes needs privilege action > ------------------------------------------------------------------------------------ > > Key: ISPN-4817 > URL: https://issues.jboss.org/browse/ISPN-4817 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 7.0.0.CR1 > Reporter: William Burns > Priority: Critical > Fix For: 7.2.0.CR1 > > > The ClusterListenerReplicateCallable needs to add the listener in a privileged block so that it can work properly. > I was also thinking if we need to change all of our messages to send along the current Subject so it can be properly applied to remote invocations as well. In this case we wouldn't need to wrap the listener invocation. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4899) Update user guide regarding protobuf schema definition API

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4899?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4899: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Update user guide regarding protobuf schema definition API > ---------------------------------------------------------- > > Key: ISPN-4899 > URL: https://issues.jboss.org/browse/ISPN-4899 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Affects Versions: 7.0.0.CR2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1 > > > Describe the usage of __protobuf_metadata cache -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4879) Log a clear error message when an incompatible node joins the cluster

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4879?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4879: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Log a clear error message when an incompatible node joins the cluster > --------------------------------------------------------------------- > > Key: ISPN-4879 > URL: https://issues.jboss.org/browse/ISPN-4879 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 7.0.0.CR2 > Reporter: Dan Berindei > Fix For: 7.2.0.CR1 > > > We don't check the Infinispan version when a node joins the cluster. If the node has an incompatible version, it will most likely fail to join, but the error message is not at all straightforward. As an example: > {noformat} > Exception in thread "main" org.infinispan.commons.CacheException: Unable > to invoke method public void > org.infinispan.statetransfer.StateTransferManagerImpl.start() throws > java.lang.Exception on object of type StateTransferManagerImpl > at > org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:170) > at > org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:869) > at > org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:638) > at > org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:627) > at > org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:530) > at > org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:216) > at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:764) > at > org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:584) > at > org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:539) > at > org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:416) > at ch.nexustelecom.lbd.engine.ImsiCache.init(ImsiCache.java:49) > at > ch.nexustelecom.dexclient.engine.DefaultDexClientEngine.init(DefaultDexClientEngine.java:120) > at ch.nexustelecom.dexclient.DexClient.initClient(DexClient.java:169) > at > ch.nexustelecom.dexclient.tool.DexClientManager.startup(DexClientManager.java:196) > at > ch.nexustelecom.dexclient.tool.DexClientManager.main(DexClientManager.java:83) > Caused by: org.infinispan.commons.CacheException: > java.lang.ClassNotFoundException: > org.infinispan.partionhandling.impl.AvailabilityMode > at org.infinispan.commons.util.Util.rewrapAsCacheException(Util.java:655) > at > org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher.invokeRemoteCommand(CommandAwareRpcDispatcher.java:176) > at > org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:536) > at > org.infinispan.topology.LocalTopologyManagerImpl.executeOnCoordinator(LocalTopologyManagerImpl.java:388) > at > org.infinispan.topology.LocalTopologyManagerImpl.join(LocalTopologyManagerImpl.java:102) > at > org.infinispan.statetransfer.StateTransferManagerImpl.start(StateTransferManagerImpl.java:108) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at > org.infinispan.commons.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:168) > ... 14 more > Caused by: java.lang.ClassNotFoundException: > org.infinispan.partionhandling.impl.AvailabilityMode > at java.net.URLClassLoader$1.run(Unknown Source) > at java.net.URLClassLoader$1.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Unknown Source) > at > org.jboss.marshalling.AbstractClassResolver.loadClass(AbstractClassResolver.java:131) > at > org.jboss.marshalling.AbstractClassResolver.resolveClass(AbstractClassResolver.java:112) > at > org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1002) > at > org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1239) > at > org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:272) > at > org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) > at > org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41) > at > org.infinispan.topology.CacheStatusResponse$Externalizer.readObject(CacheStatusResponse.java:76) > at > org.infinispan.topology.CacheStatusResponse$Externalizer.readObject(CacheStatusResponse.java:62) > at > org.infinispan.marshall.core.ExternalizerTable$ExternalizerAdapter.readObject(ExternalizerTable.java:424) > at > org.infinispan.marshall.core.ExternalizerTable.readObject(ExternalizerTable.java:221) > at > org.infinispan.marshall.core.JBossMarshaller$ExternalizerTableProxy.readObject(JBossMarshaller.java:148) > at > org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351) > at > org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) > at > org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41) > at > org.infinispan.remoting.responses.SuccessfulResponse$Externalizer.readObject(SuccessfulResponse.java:79) > at > org.infinispan.remoting.responses.SuccessfulResponse$Externalizer.readObject(SuccessfulResponse.java:64) > at > org.infinispan.marshall.core.ExternalizerTable$ExternalizerAdapter.readObject(ExternalizerTable.java:424) > at > org.infinispan.marshall.core.ExternalizerTable.readObject(ExternalizerTable.java:221) > at > org.infinispan.marshall.core.JBossMarshaller$ExternalizerTableProxy.readObject(JBossMarshaller.java:148) > at > org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:351) > at > org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209) > at > org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41) > at > org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.objectFromObjectStream(AbstractJBossMarshaller.java:135) > at > org.infinispan.marshall.core.VersionAwareMarshaller.objectFromByteBuffer(VersionAwareMarshaller.java:101) > at > org.infinispan.commons.marshall.AbstractDelegatingMarshaller.objectFromByteBuffer(AbstractDelegatingMarshaller.java:80) > at > org.infinispan.remoting.transport.jgroups.MarshallerAdapter.objectFromBuffer(MarshallerAdapter.java:28) > at > org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:390) > at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:250) > at > org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:674) > at org.jgroups.JChannel.up(JChannel.java:733) > at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030) > at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:146) > at org.jgroups.protocols.RSVP.up(RSVP.java:190) > at org.jgroups.protocols.FRAG2.up(FRAG2.java:165) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:390) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:379) > at org.jgroups.protocols.pbcast.GMS.up(GMS.java:1042) > at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:234) > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1034) > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:752) > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:399) > at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:610) > at org.jgroups.protocols.BARRIER.up(BARRIER.java:152) > at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:155) > at org.jgroups.protocols.FD_ALL.up(FD_ALL.java:200) > at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:297) > at org.jgroups.protocols.MERGE3.up(MERGE3.java:288) > at org.jgroups.protocols.Discovery.up(Discovery.java:277) > at org.jgroups.protocols.TP.passMessageUp(TP.java:1568) > at org.jgroups.protocols.TP$MyHandler.run(TP.java:1787) > at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > {noformat} > Optionally, we could allow the user to configure an "application version" and prevent nodes with different application versions from joining the same cluster. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4851) Make SyncConsistentHashFactory the default CH factory

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4851?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4851: ----------------------------------- Fix Version/s: 7.2.0.CR1 (was: 7.2.0.Beta2) > Make SyncConsistentHashFactory the default CH factory > ----------------------------------------------------- > > Key: ISPN-4851 > URL: https://issues.jboss.org/browse/ISPN-4851 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, Core > Affects Versions: 7.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.2.0.CR1 > > > With ISPN-4682 fixed, SyncConsistentHashFactory should be good enough to be the default. It still allows for more variation in the number of owned segments per node (+/-10% owned segments and +/-20% for primary-owned segments), but that should be acceptable for most purposes. > The major advantage of SCHF is that it depends only on the cache members and not on the order they joined. Users expect a key to map to the same node in all caches (as long as the caches have the same members). > One downside of SCHF, especially for testing, is that the segment ownership differs between test runs (being based on the random address assigned to each node). However, most tests that depend on key ownership should use {{ControlledConsistentHashFactory}} anyway. > We also need to verify that the number of segments moved by SCHF is comparable to the number of segments moved by DefaultConsistentHashFactory (ISPN-3729). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2015