November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3835: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Index Update command is processed before the registry listener is triggered > --------------------------------------------------------------------------- > > Key: ISPN-3835 > URL: https://issues.jboss.org/browse/ISPN-3835 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Priority: Critical > Labels: 64QueryBlockers > Fix For: 9.4.3.Final > > > When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet. > Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event. > This leads to index update commands to be lost (with a stacktrace logged) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-4824?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4824: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > 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 > Priority: Major > Fix For: 9.4.3.Final > > > 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 (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4846) State transfer keeps trying to fetch transaction data after the cache was stopped

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-4846?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4846: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > State transfer keeps trying to fetch transaction data after the cache was stopped > --------------------------------------------------------------------------------- > > Key: ISPN-4846 > URL: https://issues.jboss.org/browse/ISPN-4846 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.0.CR1 > Reporter: Dan Berindei > Priority: Major > Fix For: 9.4.3.Final > > > StateConsumerImpl doesn't check if the cache is stopped while fetching transaction data, it only stops when it's no longer able to find providers for transactions. > However, JGroupsTransport throws a generic CacheException when the channel is stopped. The state transfer thread can enter a busy-wait loop, retrying to get the transaction data and immediately getting the CacheException, filling the log with messages like this: > {noformat} > 19:32:28,237 WARN (remote-thread-NodeN-p42592-t1:) [StateConsumerImpl] ISPN000209: Failed to retrieve transactions for segments [10, 11, 12, 13, 14, 15, 17, 16, 19, 18, 21, 20, 23, 22, 25, 24, 27, 26, 29, 28, 42, 43, 40, 41, 46, 47, 44, 45, 51, 50, 49, 48, 55, 54, 53, 52, 59, 58, 57, 56] of cache testCache from node NodeM-53416 > org.infinispan.commons.CacheException: java.lang.IllegalStateException: channel is not connected > 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.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:290) > at org.infinispan.statetransfer.StateConsumerImpl.getTransactions(StateConsumerImpl.java:766) > at org.infinispan.statetransfer.StateConsumerImpl.requestTransactions(StateConsumerImpl.java:685) > at org.infinispan.statetransfer.StateConsumerImpl.addTransfers(StateConsumerImpl.java:629) > at org.infinispan.statetransfer.StateConsumerImpl.onTopologyUpdate(StateConsumerImpl.java:331) > at org.infinispan.statetransfer.StateTransferManagerImpl.doTopologyUpdate(StateTransferManagerImpl.java:195) > at org.infinispan.statetransfer.StateTransferManagerImpl.access$000(StateTransferManagerImpl.java:43) > at org.infinispan.statetransfer.StateTransferManagerImpl$1.rebalance(StateTransferManagerImpl.java:116) > {noformat} > We should check is the cache is stopped before retrying in StateConsumerImpl.requestTransactions. I also think we should change the stop order - it would make sense to stop the remote executor threads and the RpcDispatcher before we stop the channel. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-4817?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4817: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > 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: 9.4.3.Final > > > 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 (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-4624?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4624: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > 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 > Priority: Major > Labels: partition_handling > Fix For: 9.4.3.Final > > > 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 (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

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

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-4596?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4596: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > 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 > Priority: Major > Fix For: 9.4.3.Final > > > 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 (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4584) Stricter validation of cache configurations for distributed indexes

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-4584?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4584: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Stricter validation of cache configurations for distributed indexes > ------------------------------------------------------------------- > > Key: ISPN-4584 > URL: https://issues.jboss.org/browse/ISPN-4584 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 9.4.3.Final > > > See also ISPN-4577 : it should not be allowed to configure a distributed metadata cache while the chunks cache is using local mode. > Ideally think of additional strict checks which we should apply.. suggestions? > Mitigated by ISPN-4340 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4340) Automatically setup shared indexes when indexing is enabled

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-4340?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4340: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Automatically setup shared indexes when indexing is enabled > ----------------------------------------------------------- > > Key: ISPN-4340 > URL: https://issues.jboss.org/browse/ISPN-4340 > Project: Infinispan > Issue Type: Feature Request > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Major > Labels: 64QueryBlockers > Fix For: 9.4.3.Final > > > - on replicated Caches, we should create a default index on a FSDirectory and provide some appropriate default tuning, for example enabling NRT. > - distributed Caches will need the Infinispan Directory (shared) and a master/slave backend (Infinispan IndexManager, while NRT is not compatible in this case) > We want to keep the properties configuration structure as well as an "advanced tuning" and override capabilities of the default choices. > Some more common options like sync/async indexing should probably be promoted to be controlled by the XML elements and configuration DSL excplicitly. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4286) Two concurrent putIfAbsent operations can both return null during rebalance

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-4286?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4286: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Two concurrent putIfAbsent operations can both return null during rebalance > --------------------------------------------------------------------------- > > Key: ISPN-4286 > URL: https://issues.jboss.org/browse/ISPN-4286 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.2.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: consistency > Fix For: 9.4.3.Final > > > If the cache topology changes while executing a putIfAbsent operation, the old primary owner will throw an OutdatedTopologyException, and the originator will retry on the new owner. > When retrying the PutKeyValueCommand on the new primary owner, we compare the current value with the command's new value. If they are equal, we assume that the initial command wrote the old value, and we return {{null}}. > However, the value might have been written by another putIfAbsent operation. So we could have two {{putIfAbsent(k, v)}} operations, both returning {{null}}. > {code} > A is the originator, B is the primary owner, k = null > A -> B: putIfAbsent(k, v1) > B dies before writing v, C is now primary owner > D -> C: putIfAbsent(k, v1) // another put operation from D, with the same value > C -> D: null // correct > A -> C: retry_putIfAbsent(k, v1) > C -> A: null // C assumes A is overwriting its own value, so it's also returning null > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5241) Cache topology updates should use the NO_FC flag

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-5241?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5241: ------------------------------- Fix Version/s: 9.4.3.Final (was: 9.4.2.Final) > Cache topology updates should use the NO_FC flag > ------------------------------------------------ > > Key: ISPN-5241 > URL: https://issues.jboss.org/browse/ISPN-5241 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 9.4.3.Final > > > Topology updates are sent while holding the ClusterCacheStatus lock, so they should never block. However, when MFC is present, the topology update can block waiting for enough credits. As most CacheTopologyControlCommands need to acquire the ClusterCacheStatus lock, this can easily lead to a full remote-executor pool (and OOB pool) and the appearance of a deadlock. > What's more, if one node is not responsive, it can block all the other nodes from receiving further topology updates. Topology updates should be as prompt as possible, so we should use the NO_FC flag to ensure that each node receives topology updates as soon as possible. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 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 November 2018