June 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11095) Statistics should show the number of expirations similar to eviction

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11095?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11095: ------------------------------------------ Issue Type: Enhancement (was: Feature Request) > Statistics should show the number of expirations similar to eviction > -------------------------------------------------------------------- > > Key: ISPN-11095 > URL: https://issues.redhat.com/browse/ISPN-11095 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Wolf-Dieter Fink > Assignee: Nistor Adrian > Priority: Minor > > Each cache statistic shows the number of evicted entries. > It should also count the number of expired and removed entries. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12030) BlockHound is not active on JDK 13/14

by Dan Berindei (Jira)

Dan Berindei created ISPN-12030: ----------------------------------- Summary: BlockHound is not active on JDK 13/14 Key: ISPN-12030 URL: https://issues.redhat.com/browse/ISPN-12030 Project: Infinispan Issue Type: Bug Components: Build, Test Suite Affects Versions: 11.0.0.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 11.0.1.Final BlockHound cannot instrument native methods on JDK 13+ {noformat} 15:04:47,001 FATAL (Thread-0) [Infinispan-TEST] Throwable was not caught in thread Thread[Thread-0,5,main] - exception is: java.lang.IllegalStateException: The instrumentation have failed. It looks like you're running on JDK 13+. You need to add '-XX:+AllowRedefinitionToAddDeleteMethods' JVM flag. See https://github.com/reactor/BlockHound/issues/33 for more info. {noformat} Maven profile {{java13-test}} is supposed to add flag -XX:+AllowRedefinitionToAddDeleteMethods to the fork JVM, but it doesn't work because the activation condition is incomplete (missing a {{)}} after the comma). The profile also tries to add the flag when the {{java8-test}} profile is selected from the command line, so adding the missing {{)}} is not enough. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12029) Replace Blocking Executor with an EnhancedQueueExecutor

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12029?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12029: ------------------------------ Status: Open (was: New) > Replace Blocking Executor with an EnhancedQueueExecutor > ------------------------------------------------------- > > Key: ISPN-12029 > URL: https://issues.redhat.com/browse/ISPN-12029 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final, 11.0.1.Final > > > The blocking executor today uses a simple ThreadPoolExecutor. Unfortunately, this means that we will eventually start all configured threads (since core = max and we require a queue). Setting core size to less than max is not desirable as well as it will enqueue additional tasks rather than spawn a thread. > > The EnhancedQueueExecutor does exactly what we want and also has some additional features. We should utilize this which will keep our blocking thread pool size down during times of less activity. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12029) Replace Blocking Executor with an EnhancedQueueExecutor

by Will Burns (Jira)

Will Burns created ISPN-12029: --------------------------------- Summary: Replace Blocking Executor with an EnhancedQueueExecutor Key: ISPN-12029 URL: https://issues.redhat.com/browse/ISPN-12029 Project: Infinispan Issue Type: Enhancement Components: Core Reporter: Will Burns Assignee: Will Burns Fix For: 12.0.0.Final, 11.0.1.Final The blocking executor today uses a simple ThreadPoolExecutor. Unfortunately, this means that we will eventually start all configured threads (since core = max and we require a queue). Setting core size to less than max is not desirable as well as it will enqueue additional tasks rather than spawn a thread. The EnhancedQueueExecutor does exactly what we want and also has some additional features. We should utilize this which will keep our blocking thread pool size down during times of less activity. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12002) Rolling Upgrades location aware data retrieving

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12002?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-12002: ------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8492 > Rolling Upgrades location aware data retrieving > ----------------------------------------------- > > Key: ISPN-12002 > URL: https://issues.redhat.com/browse/ISPN-12002 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 9.4.19.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > Currently the Rolling upgrades data retrieval is done using several tasks in parallel, where each task retrieves from the source cluster a subset of the data from one or more segments. > Each task should only retrieve data from segments that are confined to a single source server, to avoid further remote calls inside the source server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12002) Rolling Upgrades location aware data retrieving

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-12002?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-12002: ------------------------------------- Status: Open (was: New) > Rolling Upgrades location aware data retrieving > ----------------------------------------------- > > Key: ISPN-12002 > URL: https://issues.redhat.com/browse/ISPN-12002 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Affects Versions: 9.4.19.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > Currently the Rolling upgrades data retrieval is done using several tasks in parallel, where each task retrieves from the source cluster a subset of the data from one or more segments. > Each task should only retrieve data from segments that are confined to a single source server, to avoid further remote calls inside the source server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-144) Upgrade to log4j2 ver. 2.13.2 and make it a test dependency only

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-144?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-144: --------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 4.4.0.Alpha1 4.3.4.Final Resolution: Done merged in master and 4.3.x > Upgrade to log4j2 ver. 2.13.2 and make it a test dependency only > ---------------------------------------------------------------- > > Key: IPROTO-144 > URL: https://issues.redhat.com/browse/IPROTO-144 > Project: Infinispan ProtoStream > Issue Type: Component Upgrade > Affects Versions: 4.3.3.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.4.0.Alpha1, 4.3.4.Final > > > The real logging dependency is on jboss logging, log4j is just a back end that does not need to be exposed. Also, we need to upgrade to log4j2. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-144) Upgrade to log4j2 ver. 2.13.2 and make it a test dependency only

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-144?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-144: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/protostream/pull/99, https://github.com/infinispan/protostream/pull/100 > Upgrade to log4j2 ver. 2.13.2 and make it a test dependency only > ---------------------------------------------------------------- > > Key: IPROTO-144 > URL: https://issues.redhat.com/browse/IPROTO-144 > Project: Infinispan ProtoStream > Issue Type: Component Upgrade > Affects Versions: 4.3.3.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > > The real logging dependency is on jboss logging, log4j is just a back end that does not need to be exposed. Also, we need to upgrade to log4j2. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-144) Upgrade to log4j2 ver. 2.13.2 and make it a test dependency only

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-144?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-144: --------------------------------- Sprint: DataGrid Sprint #46 > Upgrade to log4j2 ver. 2.13.2 and make it a test dependency only > ---------------------------------------------------------------- > > Key: IPROTO-144 > URL: https://issues.redhat.com/browse/IPROTO-144 > Project: Infinispan ProtoStream > Issue Type: Component Upgrade > Affects Versions: 4.3.3.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > > The real logging dependency is on jboss logging, log4j is just a back end that does not need to be exposed. Also, we need to upgrade to log4j2. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-144) Upgrade to log4j2 ver. 2.13.2 and make it a test dependency only

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-144?page=com.atlassian.jira.plugi... ] Nistor Adrian reassigned IPROTO-144: ------------------------------------ Assignee: Nistor Adrian > Upgrade to log4j2 ver. 2.13.2 and make it a test dependency only > ---------------------------------------------------------------- > > Key: IPROTO-144 > URL: https://issues.redhat.com/browse/IPROTO-144 > Project: Infinispan ProtoStream > Issue Type: Component Upgrade > Affects Versions: 4.3.3.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > > The real logging dependency is on jboss logging, log4j is just a back end that does not need to be exposed. Also, we need to upgrade to log4j2. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 June 2020