August 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12246) Docs: Details about purge with shared stores

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-12246?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-12246: ------------------------------- Labels: (was: eviction) > Docs: Details about purge with shared stores > -------------------------------------------- > > Key: ISPN-12246 > URL: https://issues.redhat.com/browse/ISPN-12246 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 12.0.0.Dev01 > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 12.0.0.Dev03 > > > chapter 8.2. Eviction ([https://infinispan.org/docs/dev/titles/configuring/configuring.html#evict...] > Starts with a sentence that leads confusion > "Eviction lets you control the size of the data container by removing cache entries to make space when adding new entries." > > The wording "removing cache entries to make space" sound like the entry will be removed like a remove('key') invocation or expiration. > But this is not the case. It should be clear that the entry is evicted from memory on exactly this instance, no other instance is affected. > To prevent from not deterministic behaviour if different instances within the cluster are used for request eviction should not be configured without persistence (as mentioned) but the initial statement should be more precise > > Proposal > Eviction lets you contol the size of data container in this local instance by dropping (evict) one choosen entry from memory only without further effects. > This is a local action for this node and does not affect any other node within the cluster > To prevent from inconsistency eviction should not be used without a configured persistence > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12246) Docs: Details about purge with shared stores

by Donald Naro (Jira)

Donald Naro created ISPN-12246: ---------------------------------- Summary: Docs: Details about purge with shared stores Key: ISPN-12246 URL: https://issues.redhat.com/browse/ISPN-12246 Project: Infinispan Issue Type: Enhancement Components: Documentation Affects Versions: 12.0.0.Dev01 Reporter: Donald Naro Assignee: Donald Naro Fix For: 12.0.0.Dev03 chapter 8.2. Eviction ([https://infinispan.org/docs/dev/titles/configuring/configuring.html#evict...] Starts with a sentence that leads confusion "Eviction lets you control the size of the data container by removing cache entries to make space when adding new entries." The wording "removing cache entries to make space" sound like the entry will be removed like a remove('key') invocation or expiration. But this is not the case. It should be clear that the entry is evicted from memory on exactly this instance, no other instance is affected. To prevent from not deterministic behaviour if different instances within the cluster are used for request eviction should not be configured without persistence (as mentioned) but the initial statement should be more precise Proposal Eviction lets you contol the size of data container in this local instance by dropping (evict) one choosen entry from memory only without further effects. This is a local action for this node and does not affect any other node within the cluster To prevent from inconsistency eviction should not be used without a configured persistence -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12173) Explanation for eviction leads confusion

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-12173?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-12173: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 12.0.0.Dev03 Resolution: Done > Explanation for eviction leads confusion > ---------------------------------------- > > Key: ISPN-12173 > URL: https://issues.redhat.com/browse/ISPN-12173 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 12.0.0.Dev01 > Reporter: Wolf-Dieter Fink > Assignee: Donald Naro > Priority: Major > Labels: eviction > Fix For: 12.0.0.Dev03 > > > chapter 8.2. Eviction ([https://infinispan.org/docs/dev/titles/configuring/configuring.html#evict...] > Starts with a sentence that leads confusion > "Eviction lets you control the size of the data container by removing cache entries to make space when adding new entries." > > The wording "removing cache entries to make space" sound like the entry will be removed like a remove('key') invocation or expiration. > But this is not the case. It should be clear that the entry is evicted from memory on exactly this instance, no other instance is affected. > To prevent from not deterministic behaviour if different instances within the cluster are used for request eviction should not be configured without persistence (as mentioned) but the initial statement should be more precise > > Proposal > Eviction lets you contol the size of data container in this local instance by dropping (evict) one choosen entry from memory only without further effects. > This is a local action for this node and does not affect any other node within the cluster > To prevent from inconsistency eviction should not be used without a configured persistence > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HRJS-89) Implement SASL security features

by Pedro Zapata Fernandez (Jira)

Pedro Zapata Fernandez created HRJS-89: ------------------------------------------ Summary: Implement SASL security features Key: HRJS-89 URL: https://issues.redhat.com/browse/HRJS-89 Project: Infinispan Javascript client Issue Type: Feature Request Reporter: Galder Zamarreño Assignee: Katia Aresti Fix For: 12.0.0.Final EXTERNAL PLAIN DIGEST-MD5 OAUTH SCRAM [https://github.com/jaredhanson/js-sasl] https://github.com/legastero/js-sasl-scram-sha-1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12245) Throttle "no route to" log messages

by Diego Lovison (Jira)

Diego Lovison created ISPN-12245: ------------------------------------ Summary: Throttle "no route to" log messages Key: ISPN-12245 URL: https://issues.redhat.com/browse/ISPN-12245 Project: Infinispan Issue Type: Bug Components: Cross-Site Replication Affects Versions: 12.0.0.Dev01, 11.0.3.Final Reporter: Diego Lovison When doing some put in a cache that has a backup site, if the backup site is not available, a lot of messages will be printed in logs. I think that we can count and print every 100 or 1000 Current state: {noformat} [1;31m21:42:38,542 ERROR (jgroups-146,edg-perf05-62972) [org.jgroups.protocols.relay.RELAY2] edg-perf05-62972: no route to site01: dropping message[m [1;31m21:42:38,542 ERROR (irac-sender-thread-edg-perf05-62972) [org.jgroups.protocols.relay.RELAY2] edg-perf05-62972: no route to site01: dropping message[m {noformat} Desired state: dropping X messages {noformat} [1;31m21:42:38,542 ERROR (irac-sender-thread-edg-perf05-62972) [org.jgroups.protocols.relay.RELAY2] edg-perf05-62972: no route to site01: dropping X messages[m {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12211) Throttle "no route to" log messages

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-12211?page=com.atlassian.jira.plugi... ] Diego Lovison updated ISPN-12211: --------------------------------- Summary: Throttle "no route to" log messages (was: Combine no route to log messages) > Throttle "no route to" log messages > ----------------------------------- > > Key: ISPN-12211 > URL: https://issues.redhat.com/browse/ISPN-12211 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 12.0.0.Dev01, 11.0.3.Final > Reporter: Diego Lovison > Priority: Major > > When doing some put in a cache that has a backup site, if the backup site is not available, a lot of messages will be printed in logs. I think that we can count and print every 100 or 1000 > Current state: > {noformat} > [1;31m21:42:38,542 ERROR (jgroups-146,edg-perf05-62972) [org.jgroups.protocols.relay.RELAY2] edg-perf05-62972: no route to site01: dropping message[m > [1;31m21:42:38,542 ERROR (irac-sender-thread-edg-perf05-62972) [org.jgroups.protocols.relay.RELAY2] edg-perf05-62972: no route to site01: dropping message[m > {noformat} > Desired state: dropping X messages > {noformat} > [1;31m21:42:38,542 ERROR (irac-sender-thread-edg-perf05-62972) [org.jgroups.protocols.relay.RELAY2] edg-perf05-62972: no route to site01: dropping X messages[m > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12242) BlockingManager add reentrant blocking scheduler

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12242?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12242: ------------------------------ Status: Open (was: New) > BlockingManager add reentrant blocking scheduler > ------------------------------------------------ > > Key: ISPN-12242 > URL: https://issues.redhat.com/browse/ISPN-12242 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Ryan Emerson > Assignee: Will Burns > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12242) BlockingManager add reentrant blocking scheduler

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12242?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12242: ------------------------------ Fix Version/s: 12.0.0.Final > BlockingManager add reentrant blocking scheduler > ------------------------------------------------ > > Key: ISPN-12242 > URL: https://issues.redhat.com/browse/ISPN-12242 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Ryan Emerson > Assignee: Will Burns > Priority: Major > Fix For: 12.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12242) BlockingManager add reentrant blocking scheduler

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12242?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12242: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8637 > BlockingManager add reentrant blocking scheduler > ------------------------------------------------ > > Key: ISPN-12242 > URL: https://issues.redhat.com/browse/ISPN-12242 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Ryan Emerson > Assignee: Will Burns > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-12244) Remove RxJavaInterop duplication from core

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-12244?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-12244: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove RxJavaInterop duplication from core > ------------------------------------------ > > Key: ISPN-12244 > URL: https://issues.redhat.com/browse/ISPN-12244 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 12.0.0.Dev02 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 12.0.0.Dev03 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2020