January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11166) SocketTimeoutFailureRetryTest random failures

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11166?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11166: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7745 > SocketTimeoutFailureRetryTest random failures > --------------------------------------------- > > Key: ISPN-11166 > URL: https://issues.redhat.com/browse/ISPN-11166 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite > Affects Versions: 10.1.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.1.1.Final > > > Replicated non-tx caches without stores have an optimization for get operations to bypass the interceptor chain and query the data container directly. The optimization was added with the non-blocking listener changes, in order to compensate their overhead, but it only covered {{get()}} and {{getAsync()}}, while the HotRod server uses {{getCacheEntryAsync()}}. > The ISPN-11020 fix extended the replicated get optimization to {{getCacheEntryAsync()}}, so now HotRod replicated reads bypass the interceptor chain, including the {{DelayingInterceptor}} added by {{SocketTimeoutFailureRetryTest}}. > {noformat} > java.lang.AssertionError: expected:<1> but was:<0> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:170) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:177) > at org.infinispan.client.hotrod.retry.SocketTimeoutFailureRetryTest.testRetrySocketTimeout(SocketTimeoutFailureRetryTest.java:68) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11171) [9.4.x] Clustered max idle doc updates

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11171?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-11171. ------------------------------ Resolution: Rejected > [9.4.x] Clustered max idle doc updates > -------------------------------------- > > Key: ISPN-11171 > URL: https://issues.redhat.com/browse/ISPN-11171 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > whenever an entry is read that can expire via max idle, we send a touch command to all owners so they all have the same relative access time. the get won't return until the touch command has completed. > scattered the backup can be any node and we don't know which nodes are backups. in this case the touch command goes to all nodes. > if you have max idle and eviction, any access of an entry on any node will update the eviction recency on all owners as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11170) Infinispan directory does not work with pre-declared indexed entities

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11170?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11170: --------------------------------- Fix Version/s: 9.4.18.Final > Infinispan directory does not work with pre-declared indexed entities > --------------------------------------------------------------------- > > Key: ISPN-11170 > URL: https://issues.redhat.com/browse/ISPN-11170 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.2.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.1.Final, 9.4.18.Final > > > This config combination leads to a circular initialisation dependency of the infinispan directory which has the potential to lead to deadlock, depending on the order the user cache and the infinispan directory's internal caches are started. > This problem of cache dependencies was always known and the LifecycleManager of query module has code to mitigate it. Unfortunately the code is wrong. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11171) [9.4.x] Clustered max idle doc updates

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11171?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11171: ------------------------------- Git Pull Request: (was: https://github.com/infinispan/infinispan/pull/7742) > [9.4.x] Clustered max idle doc updates > -------------------------------------- > > Key: ISPN-11171 > URL: https://issues.redhat.com/browse/ISPN-11171 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > whenever an entry is read that can expire via max idle, we send a touch command to all owners so they all have the same relative access time. the get won't return until the touch command has completed. > scattered the backup can be any node and we don't know which nodes are backups. in this case the touch command goes to all nodes. > if you have max idle and eviction, any access of an entry on any node will update the eviction recency on all owners as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11171) [9.4.x] Clustered max idle doc updates

by Donald Naro (Jira)

Donald Naro created ISPN-11171: ---------------------------------- Summary: [9.4.x] Clustered max idle doc updates Key: ISPN-11171 URL: https://issues.redhat.com/browse/ISPN-11171 Project: Infinispan Issue Type: Enhancement Components: Documentation Reporter: Donald Naro Assignee: Donald Naro whenever an entry is read that can expire via max idle, we send a touch command to all owners so they all have the same relative access time. the get won't return until the touch command has completed. scattered the backup can be any node and we don't know which nodes are backups. in this case the touch command goes to all nodes. if you have max idle and eviction, any access of an entry on any node will update the eviction recency on all owners as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11170) Infinispan directory does not work with pre-declared indexed entities

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11170?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11170: --------------------------------- Fix Version/s: 10.1.1.Final > Infinispan directory does not work with pre-declared indexed entities > --------------------------------------------------------------------- > > Key: ISPN-11170 > URL: https://issues.redhat.com/browse/ISPN-11170 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.2.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.1.Final, 9.4.18.Final > > > This config combination leads to a circular initialisation dependency of the infinispan directory which has the potential to lead to deadlock, depending on the order the user cache and the infinispan directory's internal caches are started. > This problem of cache dependencies was always known and the LifecycleManager of query module has code to mitigate it. Unfortunately the code is wrong. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11170) Infinispan directory does not work with pre-declared indexed entities

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11170?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11170: --------------------------------- Affects Version/s: 8.2.0.Final > Infinispan directory does not work with pre-declared indexed entities > --------------------------------------------------------------------- > > Key: ISPN-11170 > URL: https://issues.redhat.com/browse/ISPN-11170 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.2.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.1.Final, 9.4.18.Final > > > This config combination leads to a circular initialisation dependency of the infinispan directory which has the potential to lead to deadlock, depending on the order the user cache and the infinispan directory's internal caches are started. > This problem of cache dependencies was always known and the LifecycleManager of query module has code to mitigate it. Unfortunately the code is wrong. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11170) Infinispan directory does not work with pre-declared indexed entities

by Nistor Adrian (Jira)

Nistor Adrian created ISPN-11170: ------------------------------------ Summary: Infinispan directory does not work with pre-declared indexed entities Key: ISPN-11170 URL: https://issues.redhat.com/browse/ISPN-11170 Project: Infinispan Issue Type: Bug Components: Embedded Querying Reporter: Nistor Adrian Assignee: Nistor Adrian This config combination leads to a circular initialisation dependency of the infinispan directory which has the potential to lead to deadlock, depending on the order the user cache and the infinispan directory's internal caches are started. This problem of cache dependencies was always known and the LifecycleManager of query module has code to mitigate it. Unfortunately the code is wrong. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11170) Infinispan directory does not work with pre-declared indexed entities

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11170?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11170: --------------------------------- Status: Open (was: New) > Infinispan directory does not work with pre-declared indexed entities > --------------------------------------------------------------------- > > Key: ISPN-11170 > URL: https://issues.redhat.com/browse/ISPN-11170 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.2.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.1.Final, 9.4.18.Final > > > This config combination leads to a circular initialisation dependency of the infinispan directory which has the potential to lead to deadlock, depending on the order the user cache and the infinispan directory's internal caches are started. > This problem of cache dependencies was always known and the LifecycleManager of query module has code to mitigate it. Unfortunately the code is wrong. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11169) [9.4.x] JDBC string based cache store config out of date

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11169?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11169: ------------------------------- Description: The documentation is using outdate examples for the section "JDBC String based Cache Store" The example use xmlns="urn:infinispan:config:store:jdbc:9.2" and even when changing to 9.4 it is not working > [9.4.x] JDBC string based cache store config out of date > -------------------------------------------------------- > > Key: ISPN-11169 > URL: https://issues.redhat.com/browse/ISPN-11169 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > The documentation is using outdate examples for the section "JDBC String based Cache Store" > The example use xmlns="urn:infinispan:config:store:jdbc:9.2" and even when changing to 9.4 it is not working -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 January 2020