[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)
3 years, 9 months
[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)
3 years, 9 months
[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)
3 years, 9 months
[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)
3 years, 9 months