April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4903) ServerFailureRetrySingleOwnerTest doesn't actually test client retry

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-4903?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-4903: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > ServerFailureRetrySingleOwnerTest doesn't actually test client retry > -------------------------------------------------------------------- > > Key: ISPN-4903 > URL: https://issues.jboss.org/browse/ISPN-4903 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite - Server > Affects Versions: 7.0.0.CR2 > Reporter: Dan Berindei > Fix For: 9.0.0.Alpha2 > > Attachments: ServerFailureRetrySingleOwnerTest.java > > > With {{useSynchronization = true}} (the default, before ISPN-4166 is integrated), the {{SuspectException}} thrown by the listener is swallowed by the transaction manager and the client doesn't retry. The test doesn't pick that up because the exception is thrown _after_ the entry was updated in the data container (a regular SuspectException would be thrown before). > I changed the configuration to {{useSynchronization = false}}, but it didn't work because the {{SuspectException}} is wrapped in a {{CacheListenerException}}, so the client throws an exception instead of retrying. I also changed the test to use an interceptor instead of a listener, but then I got a {{ClassCastException}}: > {noformat} > Caused by: java.lang.ClassCastException: [B cannot be cast to org.infinispan.container.entries.CacheEntry > at org.infinispan.cache.impl.CacheImpl.getCacheEntry(CacheImpl.java:424) > at org.infinispan.cache.impl.CacheImpl.getCacheEntry(CacheImpl.java:429) > at org.infinispan.server.hotrod.Decoder2x$.customReadKey(Decoder2x.scala:285) > at org.infinispan.server.hotrod.HotRodDecoder.customDecodeKey(HotRodDecoder.scala:156) > at org.infinispan.server.core.AbstractProtocolDecoder.org$infinispan$server$core$AbstractProtocolDecoder$$decodeKey(AbstractProtocolDecoder.scala:176) > at org.infinispan.server.core.AbstractProtocolDecoder.decodeDispatch(AbstractProtocolDecoder.scala:71) ... 14 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4880) Distribution mode-friendly preloading

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-4880?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-4880: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Distribution mode-friendly preloading > ------------------------------------- > > Key: ISPN-4880 > URL: https://issues.jboss.org/browse/ISPN-4880 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Loaders and Stores > Affects Versions: 7.0.0.CR2 > Reporter: Dan Berindei > Fix For: 9.0.0.Alpha2 > > > For non-shared stores, we need a graceful restart to make sure each node receives the exact same segments after restart, and that keys aren't readable/writable until re recover all the segments. > With a shared store, however, we could replace the implicit preload with an explicit preload that can be called by the user after the cluster is fully formed. > Currently, preloading happens before the cache is a full member of the cluster, so it wants to load every key on every node. In a large cluster, that means most of the keys loaded by preload will be discarded as it joins and finds out it owns only a tiny slice of the data. > Preloaded values might be out of date before the node becomes a full member (because writes on the existing nodes will update the shared store, but not the joiner's in-memory data). The only way to avoid that is to delete everything that was preloaded on join, meaning even more lost work. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

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

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-4846?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-4846: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > 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 > Fix For: 9.0.0.Alpha2 > > > 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 (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5009) Upgrade server base to WildFly 9.0.0.Beta2

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-5009?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-5009: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Upgrade server base to WildFly 9.0.0.Beta2 > ------------------------------------------ > > Key: ISPN-5009 > URL: https://issues.jboss.org/browse/ISPN-5009 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build process, Server > Affects Versions: 7.0.2.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha2 > > > Originally it was meant to upgrade to Wildfly 8.2.0.Final but some issues where found. Upgrade still needed but upgrading to 9.0.0.Beta2 which solves issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4923) Server should allow toggling statistics at runtime

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-4923?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-4923: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Server should allow toggling statistics at runtime > -------------------------------------------------- > > Key: ISPN-4923 > URL: https://issues.jboss.org/browse/ISPN-4923 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 7.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

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

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-4824?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-4824: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > 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: 9.0.0.Alpha2 > > > 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.4.11#64026)

9 years, 12 months

1
0
0 / 0

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

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-4899?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-4899: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > 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: 9.0.0.Alpha2 > > > Describe the usage of __protobuf_metadata cache -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 12 months

1
0
0 / 0

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

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-4817?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-4817: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > 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.0.0.Alpha2 > > > 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.4.11#64026)

9 years, 12 months

1
0
0 / 0

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

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-4735?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-4735: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > 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 > Assignee: Tristan Tarrant > Fix For: 9.0.0.Alpha2 > > > 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.4.11#64026)

9 years, 12 months

1
0
0 / 0

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

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-4722?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-4722: ------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > 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: 9.0.0.Alpha2 > > > 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.4.11#64026)

9 years, 12 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 2016