[JBoss JIRA] (ISPN-12177) Persist IRAC version during shutdown
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-12177?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-12177:
-------------------------------
Status: Open (was: New)
> Persist IRAC version during shutdown
> ------------------------------------
>
> Key: ISPN-12177
> URL: https://issues.redhat.com/browse/ISPN-12177
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 11.0.1.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> The IRAC version is reset after a complete shutdown. It should be persisted in the global state to avoid unnecessary conflicts and/or data inconsistency.
> If the global state is disabled, the users have to deal with it.
> Also, make it possible to "compute" the version if the data is persisted and when receiving state from the remote site.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 months
[JBoss JIRA] (ISPN-12177) Persist IRAC version during shutdown
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-12177?page=com.atlassian.jira.plugi... ]
Work on ISPN-12177 started by Pedro Ruivo.
------------------------------------------
> Persist IRAC version during shutdown
> ------------------------------------
>
> Key: ISPN-12177
> URL: https://issues.redhat.com/browse/ISPN-12177
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Affects Versions: 11.0.1.Final
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> The IRAC version is reset after a complete shutdown. It should be persisted in the global state to avoid unnecessary conflicts and/or data inconsistency.
> If the global state is disabled, the users have to deal with it.
> Also, make it possible to "compute" the version if the data is persisted and when receiving state from the remote site.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 months
[JBoss JIRA] (ISPN-12177) Persist IRAC version during shutdown
by Pedro Ruivo (Jira)
Pedro Ruivo created ISPN-12177:
----------------------------------
Summary: Persist IRAC version during shutdown
Key: ISPN-12177
URL: https://issues.redhat.com/browse/ISPN-12177
Project: Infinispan
Issue Type: Bug
Components: Cross-Site Replication
Affects Versions: 11.0.1.Final
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
Fix For: 12.0.0.Final
The IRAC version is reset after a complete shutdown. It should be persisted in the global state to avoid unnecessary conflicts and/or data inconsistency.
If the global state is disabled, the users have to deal with it.
Also, make it possible to "compute" the version if the data is persisted and when receiving state from the remote site.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 months
[JBoss JIRA] (ISPN-12176) Docs: Separate Off Heap Config from Eviction
by Donald Naro (Jira)
Donald Naro created ISPN-12176:
----------------------------------
Summary: Docs: Separate Off Heap Config from Eviction
Key: ISPN-12176
URL: https://issues.redhat.com/browse/ISPN-12176
Project: Infinispan
Issue Type: Enhancement
Components: Documentation
Reporter: Donald Naro
Assignee: Donald Naro
In the Configuration Guide, off heap storage configuration should be de-coupled from eviction. "Configuring the Data Container" should include off heap, eviction, expiration, encoding.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 4 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:
-------------------------------
Sprint: DataGrid Sprint #47
Affects: Documentation (Ref Guide, User Guide, etc.),User Experience
> 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
>
> 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)
4 years, 4 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... ]
Work on ISPN-12173 started by Donald Naro.
------------------------------------------
> 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
>
> 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)
4 years, 4 months