April 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9087) Timeout during put operation when a node is blocked

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9087?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-9087: ---------------------------------- Assignee: Dan Berindei > Timeout during put operation when a node is blocked > --------------------------------------------------- > > Key: ISPN-9087 > URL: https://issues.jboss.org/browse/ISPN-9087 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Dan Berindei > > {noformat} > 2018-04-17 13:30:02.782 ERROR 14932 --- [timeout-thread--p3-t1] o.i.i.impl.InvocationContextInterceptor : ISPN000136: Error executing command PutKeyValueCommand, writing keys [5db796a3-3f65-468a-b86a-6d5ef8b4b330] > > org.infinispan.util.concurrent.TimeoutException: ISPN000427: Timeout after 15 seconds waiting for acks. Id=100000 > at org.infinispan.util.concurrent.CommandAckCollector.createTimeoutException(CommandAckCollector.java:188) ~[infinispan-embedded-8.5.0.Final-redhat-6.jar:8.5.0.Final-redhat-6] > at org.infinispan.util.concurrent.CommandAckCollector.access$300(CommandAckCollector.java:51) ~[infinispan-embedded-8.5.0.Final-redhat-6.jar:8.5.0.Final-redhat-6] > at org.infinispan.util.concurrent.CommandAckCollector$BaseCollector.call(CommandAckCollector.java:214) [infinispan-embedded-8.5.0.Final-redhat-6.jar:8.5.0.Final-redhat-6] > at org.infinispan.util.concurrent.CommandAckCollector$BaseCollector.call(CommandAckCollector.java:191) [infinispan-embedded-8.5.0.Final-redhat-6.jar:8.5.0.Final-redhat-6] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_161] > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_161] > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_161] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_161] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_161] > at java.lang.Thread.run(Thread.java:748) [na:1.8.0_161] > {noformat} > After some investigation together with [~dan.berindei], we found that the FD_ALL is just too slow. > {noformat} > <FD_ALL timeout="60000" > interval="15000" > timeout_check_interval="5000" > /> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9087) Timeout during put operation when a node is blocked

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9087?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9087: ------------------------------- Status: Open (was: New) > Timeout during put operation when a node is blocked > --------------------------------------------------- > > Key: ISPN-9087 > URL: https://issues.jboss.org/browse/ISPN-9087 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Dan Berindei > > {noformat} > 2018-04-17 13:30:02.782 ERROR 14932 --- [timeout-thread--p3-t1] o.i.i.impl.InvocationContextInterceptor : ISPN000136: Error executing command PutKeyValueCommand, writing keys [5db796a3-3f65-468a-b86a-6d5ef8b4b330] > > org.infinispan.util.concurrent.TimeoutException: ISPN000427: Timeout after 15 seconds waiting for acks. Id=100000 > at org.infinispan.util.concurrent.CommandAckCollector.createTimeoutException(CommandAckCollector.java:188) ~[infinispan-embedded-8.5.0.Final-redhat-6.jar:8.5.0.Final-redhat-6] > at org.infinispan.util.concurrent.CommandAckCollector.access$300(CommandAckCollector.java:51) ~[infinispan-embedded-8.5.0.Final-redhat-6.jar:8.5.0.Final-redhat-6] > at org.infinispan.util.concurrent.CommandAckCollector$BaseCollector.call(CommandAckCollector.java:214) [infinispan-embedded-8.5.0.Final-redhat-6.jar:8.5.0.Final-redhat-6] > at org.infinispan.util.concurrent.CommandAckCollector$BaseCollector.call(CommandAckCollector.java:191) [infinispan-embedded-8.5.0.Final-redhat-6.jar:8.5.0.Final-redhat-6] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_161] > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_161] > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_161] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [na:1.8.0_161] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [na:1.8.0_161] > at java.lang.Thread.run(Thread.java:748) [na:1.8.0_161] > {noformat} > After some investigation together with [~dan.berindei], we found that the FD_ALL is just too slow. > {noformat} > <FD_ALL timeout="60000" > interval="15000" > timeout_check_interval="5000" > /> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8941) RemoteCacheAdmin configuration name should use cache name

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-8941?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-8941: --------------------------------- Issue Type: Bug (was: Enhancement) Reclassifying as an actual bug, there is no way to customize the name in org.infinispan.configuration.cache.Configuration; the name is written out org.infinispan.client.hotrod.impl.RemoteCacheManagerAdminImpl#getOrCreateCache(java.lang.String, org.infinispan.commons.configuration.BasicConfiguration). So this is a breaking change as well. Wrapping org.infinispan.commons.configuration.BasicConfiguration in a fashion to woarkound hotrod logic {code} @Override public String toXMLString(String name) { ParserRegistry reg = new ParserRegistry(); return reg.serialize("configuration", configuration); }{code} breaks compatibility with future versions. > RemoteCacheAdmin configuration name should use cache name > --------------------------------------------------------- > > Key: ISPN-8941 > URL: https://issues.jboss.org/browse/ISPN-8941 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Hot Rod, Server > Affects Versions: 9.2.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.2.1.Final > > > The current implementation of the server-side for remote cache admin expects the name of the configuration in the supplied XML to be "configuration" . This would be more intuitive if it used the actual name. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8998) Automatically release from CI

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/ISPN-8998?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on ISPN-8998: -------------------------------------- The testing of this is polluting tags on master github repo :-( * [new tag] 0.0.1.Qualifier -> 0.0.1.Qualifier > Automatically release from CI > ----------------------------- > > Key: ISPN-8998 > URL: https://issues.jboss.org/browse/ISPN-8998 > Project: Infinispan > Issue Type: Bug > Components: Build, CI > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > The releases should happen via a Jenkins job: > * versioning, build and stage to nexus > * reversion and build of simple tutorials against stage repository to ensure that all artifacts are correctly published > * release and drop of nexus staging repo > * push tag and bump version to next snapshot on master branch -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9090) Create both thin and fat servers

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-9090: ------------------------------------- Summary: Create both thin and fat servers Key: ISPN-9090 URL: https://issues.jboss.org/browse/ISPN-9090 Project: Infinispan Issue Type: Bug Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.3.0.Alpha1 The server build should create two servers: * a thin one (to be pushed to maven and used for the testsuite) * a fat one (to be used as the binary distro) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9089) Conflict Resolution phase should be non-blocking and restart on node failures

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9089?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9089: ------------------------------- Status: Open (was: New) > Conflict Resolution phase should be non-blocking and restart on node failures > ----------------------------------------------------------------------------- > > Key: ISPN-9089 > URL: https://issues.jboss.org/browse/ISPN-9089 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Alpha1 > > > Currently if a node crashes during the conflict resolution phase, all topology updates and rebalancing is blocked until CR times out. As the CR timeout is the state transfer timeout, this means the cluster is in limbo for 4 minutes by default. This blocking behaviour occurs because currently the entire CR phase is executed in the merge thread, however it should occur asynchronously in a similar manner to a cache rebalance with CR restarting in the event of nodes leaving. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9089) Conflict Resolution phase should be non-blocking and restart on node failures

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-9089?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9089: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5902 > Conflict Resolution phase should be non-blocking and restart on node failures > ----------------------------------------------------------------------------- > > Key: ISPN-9089 > URL: https://issues.jboss.org/browse/ISPN-9089 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.3.0.Alpha1 > > > Currently if a node crashes during the conflict resolution phase, all topology updates and rebalancing is blocked until CR times out. As the CR timeout is the state transfer timeout, this means the cluster is in limbo for 4 minutes by default. This blocking behaviour occurs because currently the entire CR phase is executed in the merge thread, however it should occur asynchronously in a similar manner to a cache rebalance with CR restarting in the event of nodes leaving. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9089) Conflict Resolution phase should be non-blocking and restart on node failures

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-9089: ---------------------------------- Summary: Conflict Resolution phase should be non-blocking and restart on node failures Key: ISPN-9089 URL: https://issues.jboss.org/browse/ISPN-9089 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 9.2.1.Final Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 9.3.0.Alpha1 Currently if a node crashes during the conflict resolution phase, all topology updates and rebalancing is blocked until CR times out. As the CR timeout is the state transfer timeout, this means the cluster is in limbo for 4 minutes by default. This blocking behaviour occurs because currently the entire CR phase is executed in the merge thread, however it should occur asynchronously in a similar manner to a cache rebalance with CR restarting in the event of nodes leaving. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9036) Parameterized branding for C++

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9036?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9036: ------------------------------------- Status: Open (was: New) > Parameterized branding for C++ > ------------------------------ > > Key: ISPN-9036 > URL: https://issues.jboss.org/browse/ISPN-9036 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Vittorio Rigamonti > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9036) Parameterized branding for C++

by Vittorio Rigamonti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9036?page=com.atlassian.jira.plugin.... ] Vittorio Rigamonti updated ISPN-9036: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/cpp-client/pull/330 > Parameterized branding for C++ > ------------------------------ > > Key: ISPN-9036 > URL: https://issues.jboss.org/browse/ISPN-9036 > Project: Infinispan > Issue Type: Enhancement > Reporter: Tristan Tarrant > Assignee: Vittorio Rigamonti > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 2018