April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11519) Cache should not start if it cluster listener replication fails

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11519?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11519: ----------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.Dev04) > Cache should not start if it cluster listener replication fails > --------------------------------------------------------------- > > Key: ISPN-11519 > URL: https://issues.redhat.com/browse/ISPN-11519 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev05 > > > {{StateConsumerImpl.fetchClusterListeners}} catches any exceptions during the fetch and local installation of cluster listeners from other nodes, and only logs a warning message: > {noformat} > 18:04:14,069 WARN (jgroups-5,Test-NodeD:[]) [StateConsumerImpl] ISPN000284: Problem encountered while installing cluster listener > {noformat} > If a cache starts without installing all the cluster listeners locally, the listeners will miss events for keys that end up with the joiner as the primary owner, which would be pretty hard to debug. We should instea fail fast, and prevent the cache from starting if the cluster listeners cannot be fetched and installed locally. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11528) Only register HotRod module resources if the endpoint is enabled

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11528?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11528: ----------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.Dev04) > Only register HotRod module resources if the endpoint is enabled > ---------------------------------------------------------------- > > Key: ISPN-11528 > URL: https://issues.redhat.com/browse/ISPN-11528 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 11.0.0.Dev03 > Reporter: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Dev05 > > > Currently we allow the HotRod endpoint to be disabled in the server by omitting it from the xml configuration, however it's internal components and caches are unnecessarily registered regardless. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11531) HotRod Server transaction is blocking

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11531?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11531: ----------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.Dev04) > HotRod Server transaction is blocking > ------------------------------------- > > Key: ISPN-11531 > URL: https://issues.redhat.com/browse/ISPN-11531 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev05 > > > The PrepareCoordinator and TransactionRequestProcessor classes both invoke the Java JTA API which is inherently blocking. We need to handle this properly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11532) Replace HotRod thread pools

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11532?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11532: ----------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.Dev04) > Replace HotRod thread pools > --------------------------- > > Key: ISPN-11532 > URL: https://issues.redhat.com/browse/ISPN-11532 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev05 > > > The hotrod worker thread pool should use the blocking thread pool. > The netty thread pool should use the non blocking thread pool. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11535) Remove transitive dependencies from main pom.xml

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11535?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11535: ----------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.Dev04) > Remove transitive dependencies from main pom.xml > ------------------------------------------------ > > Key: ISPN-11535 > URL: https://issues.redhat.com/browse/ISPN-11535 > Project: Infinispan > Issue Type: Task > Affects Versions: 11.0.0.Dev03 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.Dev05 > > > Currently, our pom.xml has a lot of transitive dependencies. It is a problem to try to keep them align with the real dependency that uses them. It is better to remove them and later add whatever is really needed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11534) Deprecate DefaultCacheManager constructors with default configuration

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11534?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11534: ----------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.Dev04) > Deprecate DefaultCacheManager constructors with default configuration > --------------------------------------------------------------------- > > Key: ISPN-11534 > URL: https://issues.redhat.com/browse/ISPN-11534 > Project: Infinispan > Issue Type: Bug > Components: API, Core > Affects Versions: 11.0.0.Dev03 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev05 > > > {{DefaultCacheManager}} no longer has a default cache by default. In order to use the constructors with a default {{Configuration}} parameter, the user also has to define a default cache name in the {{GlobalConfiguration}}, but that is surprising. > We should remove these constructors, as the user can use the {{ConfigurationBuilderHolder}} constructor to define a default cache (and other caches as well) before starting the cache manager. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11537) Add StatefulSet rolling upgrade server integration test

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11537?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11537: ----------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.Dev04) > Add StatefulSet rolling upgrade server integration test > ------------------------------------------------------- > > Key: ISPN-11537 > URL: https://issues.redhat.com/browse/ISPN-11537 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11541) Add internal metadata to write commands

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11541?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11541: ----------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.Dev04) > Add internal metadata to write commands > --------------------------------------- > > Key: ISPN-11541 > URL: https://issues.redhat.com/browse/ISPN-11541 > Project: Infinispan > Issue Type: Sub-task > Affects Versions: 11.0.0.Dev03 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.Dev05 > > > Add the internal metadata to writes commands so it can be transferred between nodes in the cluster (via normal operations or state transfer). Also, used by cross-site replication. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11543) Add BlockingHandler to simplify running blocking operations

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11543?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11543: ----------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.Dev04) > Add BlockingHandler to simplify running blocking operations > ----------------------------------------------------------- > > Key: ISPN-11543 > URL: https://issues.redhat.com/browse/ISPN-11543 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev05 > > > We have quite a few places that must run blocking operations that cannot be changed. These places must run the operation in a blocking thread and return on a non blocking thread. All of these places must register both a blocking and non blocking thread pool and properly handle them. This is both error prone and a lot of extra code. We should isolate this to a shared component which will in turn provide for an easier way to find such operations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11553) Add BlockHound to cluster locks

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11553?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11553: ----------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.Dev04) > Add BlockHound to cluster locks > ------------------------------- > > Key: ISPN-11553 > URL: https://issues.redhat.com/browse/ISPN-11553 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Dev05 > > > Cluster Locks use a blocking pool for a few things. This should be removable, assuming functional map is properly non blocking. We should introduce block hound and find out! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 2020