January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11164) Docs: Clustered max idle updates

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11164?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11164: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Docs: Clustered max idle updates > -------------------------------- > > Key: ISPN-11164 > URL: https://issues.redhat.com/browse/ISPN-11164 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 9.4.18.Final, 11.0.0.Final, 10.1.1.Final > > > 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-11212) Ensure max idle works with passivation

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-11212?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink edited comment on ISPN-11212 at 1/23/20 11:26 AM: ------------------------------------------------------------------- I noted that a few entries (10 with ObjectSize=5) will not show the issue but 1000/500 does > Ensure max idle works with passivation > -------------------------------------- > > Key: ISPN-11212 > URL: https://issues.redhat.com/browse/ISPN-11212 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Loaders and Stores > Affects Versions: 10.1.1.Final > Reporter: Tristan Tarrant > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > We need to have tests in place that ensure that maxIdle expiration works in combination with passivation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11212) Ensure max idle works with passivation

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-11212?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink commented on ISPN-11212: ----------------------------------------- I noted that a few entries (10 with ObjectSize=5) will not show the issue but 1000/500 does > Ensure max idle works with passivation > -------------------------------------- > > Key: ISPN-11212 > URL: https://issues.redhat.com/browse/ISPN-11212 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Loaders and Stores > Affects Versions: 10.1.1.Final > Reporter: Tristan Tarrant > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > We need to have tests in place that ensure that maxIdle expiration works in combination with passivation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11218) Ensure max-idle works with enabled eviction and a configured persistence

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-11218?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink reassigned ISPN-11218: --------------------------------------- Assignee: Will Burns > Ensure max-idle works with enabled eviction and a configured persistence > ------------------------------------------------------------------------ > > Key: ISPN-11218 > URL: https://issues.redhat.com/browse/ISPN-11218 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Loaders and Stores > Affects Versions: 10.1.1.Final > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Major > > If a cache is configured with eviction and expiration max-idle, correct with a store (passivation=false) to keep the evicted entries, the cache size and entries comming down to the eviction limit after max-idle is reached. > Note this will happen no matter whether a get() or getWithMetadata() is used. > Configuration is like below. > ~~~ > <distributed-cache name="ExpirationCache" owners="2" mode="ASYNC" remote-timeout="25000" start="EAGER"> > <locking isolation="READ_COMMITTED" striping="false" acquire-timeout="20000" concurrency-level="1000"/> > <transaction mode="NONE"/> > <memory> > <object size="5"/> > </memory> > <expiration max-idle="20000" lifespan="100000"/> > <persistence passivation="false"> > <file-store max-entries="1000000" relative-to="jboss.server.data.dir" path="api-general-filestore" name="api-general-filestore" shared="false" preload="false" fetch-state="true" purge="true"/> > </persistence> > </distributed-cache> > ~~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11218) Ensure max-idle works with enabled eviction and a configured persistence

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-11218: --------------------------------------- Summary: Ensure max-idle works with enabled eviction and a configured persistence Key: ISPN-11218 URL: https://issues.redhat.com/browse/ISPN-11218 Project: Infinispan Issue Type: Bug Components: Expiration, Loaders and Stores Affects Versions: 10.1.1.Final Reporter: Wolf-Dieter Fink If a cache is configured with eviction and expiration max-idle, correct with a store (passivation=false) to keep the evicted entries, the cache size and entries comming down to the eviction limit after max-idle is reached. Note this will happen no matter whether a get() or getWithMetadata() is used. Configuration is like below. ~~~ <distributed-cache name="ExpirationCache" owners="2" mode="ASYNC" remote-timeout="25000" start="EAGER"> <locking isolation="READ_COMMITTED" striping="false" acquire-timeout="20000" concurrency-level="1000"/> <transaction mode="NONE"/> <memory> <object size="5"/> </memory> <expiration max-idle="20000" lifespan="100000"/> <persistence passivation="false"> <file-store max-entries="1000000" relative-to="jboss.server.data.dir" path="api-general-filestore" name="api-general-filestore" shared="false" preload="false" fetch-state="true" purge="true"/> </persistence> </distributed-cache> ~~~ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11212) Ensure max idle works with passivation

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-11212?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink commented on ISPN-11212: ----------------------------------------- It seems working with local caches, only distributed/replicated are affected. Configuration is like below. If the entry is read by a simple get() it will drop after max-idle to a random number <"memory object size" if the entry is read by getWithMetadata the entries are kept until lifespan is reached! ~~~ <distributed-cache name="ExpirationCache" owners="2" mode="ASYNC" remote-timeout="25000" start="EAGER"> <locking isolation="READ_COMMITTED" striping="false" acquire-timeout="20000" concurrency-level="1000"/> <transaction mode="NONE"/> <memory> <object size="100"/> </memory> <expiration max-idle="20000" lifespan="300000"/> <persistence passivation="true"> <file-store max-entries="1000000" relative-to="jboss.server.data.dir" path="api-general-filestore" name="api-general-filestore" shared="false" preload="false" fetch-state="true" purge="true"/> </persistence> </distributed-cache> ~~~ > Ensure max idle works with passivation > -------------------------------------- > > Key: ISPN-11212 > URL: https://issues.redhat.com/browse/ISPN-11212 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Loaders and Stores > Affects Versions: 10.1.1.Final > Reporter: Tristan Tarrant > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Final > > > We need to have tests in place that ensure that maxIdle expiration works in combination with passivation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11195) InfinispanEmbeddedAutoConfiguration starts DefaultCacheManager too early

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11195?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11195: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan-spring-boot/pull/131, https://github.com/infinispan/infinispan-spring-boot/pull/132 (was: https://github.com/infinispan/infinispan-spring-boot/pull/131) > InfinispanEmbeddedAutoConfiguration starts DefaultCacheManager too early > ------------------------------------------------------------------------ > > Key: ISPN-11195 > URL: https://issues.redhat.com/browse/ISPN-11195 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Details : https://github.com/infinispan/infinispan-spring-boot/issues/130 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11195) InfinispanEmbeddedAutoConfiguration starts DefaultCacheManager too early

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11195?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11195: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-spring-boot/pull/131 > InfinispanEmbeddedAutoConfiguration starts DefaultCacheManager too early > ------------------------------------------------------------------------ > > Key: ISPN-11195 > URL: https://issues.redhat.com/browse/ISPN-11195 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Details : https://github.com/infinispan/infinispan-spring-boot/issues/130 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11195) InfinispanEmbeddedAutoConfiguration starts DefaultCacheManager too early

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11195?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11195: -------------------------------- Status: Open (was: New) > InfinispanEmbeddedAutoConfiguration starts DefaultCacheManager too early > ------------------------------------------------------------------------ > > Key: ISPN-11195 > URL: https://issues.redhat.com/browse/ISPN-11195 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Details : https://github.com/infinispan/infinispan-spring-boot/issues/130 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11217) Elytron 1.11.0.Final

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11217: -------------------------------------- Summary: Elytron 1.11.0.Final Key: ISPN-11217 URL: https://issues.redhat.com/browse/ISPN-11217 Project: Infinispan Issue Type: Component Upgrade Components: Build, Security Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 11.0.0.Alpha1 -- 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