March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11481) Infinispan shutdownHook should not be registered in Embedded mode

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11481?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11481: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > Infinispan shutdownHook should not be registered in Embedded mode > ----------------------------------------------------------------- > > Key: ISPN-11481 > URL: https://issues.redhat.com/browse/ISPN-11481 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 11.0.0.Alpha2 > Reporter: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Dev04 > > > Currently the GlobalComponentRegistry registers a shutdown hook with the JVM, however for Embedded mode this does not necessarily makes sense as it should be up to the consuming application to control this behaviour. Instead, we just register this shutdown hook on the server runtime. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11485) No Server logs after shutdownHook has been called

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11485?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11485: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > No Server logs after shutdownHook has been called > ------------------------------------------------- > > Key: ISPN-11485 > URL: https://issues.redhat.com/browse/ISPN-11485 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Alpha2, 10.1.5.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Dev04, 10.1.6.Final > > > When a server process receives a SIGTERM it simply logs the following, regardless of the log configuration: > {code} > INFO (Thread-0) [org.infinispan.SERVER] ISPN080002: Infinispan Server stopping > INFO (Thread-0) [org.infinispan.SERVER] ISPN080002: Infinispan Server stopped > {code} > This is because Log4j registers a shutdownHook with the runtime in order to cleanup log resources. In order to aid server debugging, we should [disable this shutdownHook|https://logging.apache.org/log4j/2.x/manual/configuration.html] and manually shutdown the Log4j LogManager. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11474) RecoveryManager API should be non blocking

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11474?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11474: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > RecoveryManager API should be non blocking > ------------------------------------------ > > Key: ISPN-11474 > URL: https://issues.redhat.com/browse/ISPN-11474 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > RecoverManager, which is internal only, has a blocking API which can pass a sync parameter. Instead we should change the API to be non blocking and let callers decide if they want to wait or not on it. This allows us to clean up callers who may be able to use this in a non blocking fashion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11470) Scheduled thread pools rejection handle should throw Lifecycle exception

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11470?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11470: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > Scheduled thread pools rejection handle should throw Lifecycle exception > ------------------------------------------------------------------------ > > Key: ISPN-11470 > URL: https://issues.redhat.com/browse/ISPN-11470 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > This can manifest issues like https://ci.infinispan.org/job/Infinispan/job/master/1856/testReport/junit... > In this case when the node is shutting down we shouldn't be throwing such errors and instead it should be a IllegalLifecycleStateException so that other nodes know it was due to it shutting down. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11480) GlobalComponentRegistry shutdownHook should call EmbeddedCacheManager#stop

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11480?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11480: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > GlobalComponentRegistry shutdownHook should call EmbeddedCacheManager#stop > -------------------------------------------------------------------------- > > Key: ISPN-11480 > URL: https://issues.redhat.com/browse/ISPN-11480 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 11.0.0.Alpha2, 10.1.5.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 11.0.0.Dev04, 10.1.6.Final > > > Currently if a SIGTERM is called on a Infinispan processor, the shutdown hook calls {{GlobalComponentRegistry::stop}} which results in caches not leaving the cluster gracefully. In particular this affects the behaviour of 2 node Infinispan clusters when utlised in a Kubernetes StatefulSet, as it will result in the cluster becoming degraded during a rolling upgrade. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11489) TransactionCoordinator updated for non blocking

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11489?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11489: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > TransactionCoordinator updated for non blocking > ----------------------------------------------- > > Key: ISPN-11489 > URL: https://issues.redhat.com/browse/ISPN-11489 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > TransactionCoordinator is utilized when working with transactions. Unfortunately due to transaction API being inherently blocking, we need to make some exceptions to how this is handled. > # TransactionCoordinator should only be invokable by a blocking method, the inverse of the PersistenceManagerImpl > # We should invoke all the non blocking code of TransactionCoordinator in a non blocking thread and then block on its completion in the blocking thread. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11465) Upgrade to JGroups 4.2.1.Final

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11465?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11465: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > Upgrade to JGroups 4.2.1.Final > ------------------------------ > > Key: ISPN-11465 > URL: https://issues.redhat.com/browse/ISPN-11465 > Project: Infinispan > Issue Type: Component Upgrade > Components: Dependency > Affects Versions: 11.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev04 > > > JGroups 4.2.1 includes a fix for JGRP-2435, which should fix the random failure in {{InitialClusterSizeTest}}. > JGRP-2451 also adds a new failure detection protocol, {{FD3_ALL}}, which doesn't need extra heartbeats as long as the nodes are sending other broadcast messages. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11463) Cache manager stats are mistakenly exported as MP metrics even when stats disabled

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11463?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11463: ----------------------------------- Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev03) > Cache manager stats are mistakenly exported as MP metrics even when stats disabled > ---------------------------------------------------------------------------------- > > Key: ISPN-11463 > URL: https://issues.redhat.com/browse/ISPN-11463 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev04, 10.1.6.Final > > > The exported values are meaningless, constant, 0 or in some cases -1. It would be better not to register those metrics at all in this case. Actually, that was the initial, documented, intention but we have a small bug. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10608) Docs: Embedded

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10608?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10608: ------------------------------- Status: Open (was: New) > Docs: Embedded > -------------- > > Key: ISPN-10608 > URL: https://issues.redhat.com/browse/ISPN-10608 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Provide a simple, lightweight doc. Add dependencies, instantiate a cm, create a cache. Then point to the weatherapp tutorial for more detailed learning. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10608) Docs: Embedded

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10608?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10608: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8074 > Docs: Embedded > -------------- > > Key: ISPN-10608 > URL: https://issues.redhat.com/browse/ISPN-10608 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Provide a simple, lightweight doc. Add dependencies, instantiate a cm, create a cache. Then point to the weatherapp tutorial for more detailed learning. -- 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 March 2020