March 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10072) Core module should export reactive-streams for store implementations

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10072?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10072: ----------------------------------- Fix Version/s: 9.4.12.Final (was: 9.4.11.Final) > Core module should export reactive-streams for store implementations > -------------------------------------------------------------------- > > Key: ISPN-10072 > URL: https://issues.jboss.org/browse/ISPN-10072 > Project: Infinispan > Issue Type: Enhancement > Components: Server, WildFly modules > Affects Versions: 10.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > As the persistence SPI now depends on reactive-streams for the Publisher based methods, we should make the core infinispan module export these dependencies so that it's not necessary for every store implementation to explicitly define the dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10070) DefaultCacheManager should stop components after start failure

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10070?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10070: ----------------------------------- Fix Version/s: 9.4.12.Final (was: 9.4.11.Final) > DefaultCacheManager should stop components after start failure > -------------------------------------------------------------- > > Key: ISPN-10070 > URL: https://issues.jboss.org/browse/ISPN-10070 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > Currently it is impossible to release all the resources allocated during startup if the {{DefaultCacheManager}} instance was created with {{start=true}}. The user has to do something like this: > {code:java} > DefaultCacheManager manager = new DefaultCacheManager(..., false); > try { > manager.start(); > } catch (Throwable t) { > manager.stop(); > throw t; > } > {code} > Both the constructor and the public {{start()}} method should clean up the started components after a startup failure, so that the user doesn't have to call {{stop()}} explicitly. > Our tests do not currently call {{stop()}} explicitly, so they leak threads and sockets when a manager fails to start (e.g. because something went wrong with the {{CONFIG}} cache). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10062) Docs refer to infinispan-cli-server instead of infinispan-cli-interpreter

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10062?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10062: ----------------------------------- Fix Version/s: 9.4.12.Final (was: 9.4.11.Final) > Docs refer to infinispan-cli-server instead of infinispan-cli-interpreter > ------------------------------------------------------------------------- > > Key: ISPN-10062 > URL: https://issues.jboss.org/browse/ISPN-10062 > Project: Infinispan > Issue Type: Bug > Components: Documentation-Core > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10051) Cluster stats error after node leaves

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10051?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10051: ----------------------------------- Fix Version/s: 9.4.12.Final (was: 9.4.11.Final) > Cluster stats error after node leaves > ------------------------------------- > > Key: ISPN-10051 > URL: https://issues.jboss.org/browse/ISPN-10051 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.4.9.Final > Reporter: Dan Berindei > Assignee: William Burns > Priority: Major > Fix For: 9.4.12.Final > > > Up to 9.4.x, {{ClusterCacheStatsImpl}} uses the distributed executor service to collect statistics from all the members of the cache. However, DES will fail with a {{SuspectException}} if one of the cache members is no longer in the cluster view, which is very common (a crashed node is always removed from the cluster view first and from the cache topology later): > {noformat} > 23:40:57,029 ERROR [org.infinispan.stats.impl.ClusterCacheStatsImpl] (pool-1-thread-1) Could not execute cluster wide cache stats operation : java.util.concurrent.ExecutionException: > org.infinispan.remoting.transport.jgroups.SuspectException: ISPN000400: Node rhdg73-server-11-9pl9h was suspected > {noformat} > In 10.0.x the distributed executor was removed and stats use the cluster executor, which only works with the cluster view. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10040) Embedded and server thread pool defaults should be the same

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10040?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10040: ----------------------------------- Fix Version/s: 9.4.12.Final (was: 9.4.11.Final) > Embedded and server thread pool defaults should be the same > ----------------------------------------------------------- > > Key: ISPN-10040 > URL: https://issues.jboss.org/browse/ISPN-10040 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 8.2.11.Final, 10.0.0.Beta2, 9.4.9.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > Embedded: > {code:java} > DEFAULT_THREAD_COUNT.put(REMOTE_COMMAND_EXECUTOR, 200); > DEFAULT_QUEUE_SIZE.put(REMOTE_COMMAND_EXECUTOR, 0); > {code} > Server: > {code:java} > REMOTE_COMMAND("remote-command", 25, 25, 100000, 60000), > {code} > Using a huge queue is not ok for the remote thread pool, but I missed it before because I assumed the server was using the {{KnownComponentNames}} defaults. We should unify the thread pool defaults in another class with a more topical name and remove {{KnownComponentNames}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9852) Invocations waiting for a new topology should resume in parallel

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9852?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9852: ---------------------------------- Fix Version/s: 9.4.12.Final (was: 9.4.11.Final) > Invocations waiting for a new topology should resume in parallel > ---------------------------------------------------------------- > > Key: ISPN-9852 > URL: https://issues.jboss.org/browse/ISPN-9852 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.2.11.Final, 10.0.0.Alpha2, 9.4.5.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > When a command requires a topology newer than the current topology, it uses {{StateTransferLock.transactionDataFuture()}} to wait for the newer topology. When the tx data is received for the newer topology, some (most?) of the waiting operations do not use a separate executor, instead they are all resumed on the thread that received the tx data. If some operations block (e.g. because of a store), it could take a very long time to finish all the blocked operations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10079) Upgrade to jboss-modules 1.8.7.Final

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10079?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10079: ----------------------------------- Fix Version/s: 10.0.0.Beta4 (was: 10.0.0.Beta3) > Upgrade to jboss-modules 1.8.7.Final > ------------------------------------ > > Key: ISPN-10079 > URL: https://issues.jboss.org/browse/ISPN-10079 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > Includes fix for MODULES-375 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10074) DefaultSegmentedDataContainer executeTask() and iterator() include expired entries

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10074?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10074: ----------------------------------- Fix Version/s: 10.0.0.Beta4 (was: 10.0.0.Beta3) > DefaultSegmentedDataContainer executeTask() and iterator() include expired entries > ---------------------------------------------------------------------------------- > > Key: ISPN-10074 > URL: https://issues.jboss.org/browse/ISPN-10074 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > The {{executeTask()}} javadoc doesn't mention expired entries, but {{iterator()}}'s says they shouldn't be included, and non-segmented containers do not include them. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10072) Core module should export reactive-streams for store implementations

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10072?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10072: ----------------------------------- Fix Version/s: 10.0.0.Beta4 (was: 10.0.0.Beta3) > Core module should export reactive-streams for store implementations > -------------------------------------------------------------------- > > Key: ISPN-10072 > URL: https://issues.jboss.org/browse/ISPN-10072 > Project: Infinispan > Issue Type: Enhancement > Components: Server, WildFly modules > Affects Versions: 10.0.0.Beta2 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > As the persistence SPI now depends on reactive-streams for the Publisher based methods, we should make the core infinispan module export these dependencies so that it's not necessary for every store implementation to explicitly define the dependency. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10079) Upgrade to jboss-modules 1.8.7.Final

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10079?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10079: ----------------------------------- Fix Version/s: 9.4.12.Final (was: 9.4.11.Final) > Upgrade to jboss-modules 1.8.7.Final > ------------------------------------ > > Key: ISPN-10079 > URL: https://issues.jboss.org/browse/ISPN-10079 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 10.0.0.Beta2, 9.4.10.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta4, 9.4.12.Final > > > Includes fix for MODULES-375 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2019