[
https://issues.jboss.org/browse/ISPN-7168?page=com.atlassian.jira.plugin....
]
William Burns updated ISPN-7168:
--------------------------------
Description:
Passivation only makes sense with a non shared cache store. --The problem is that if an
entry is passivated on a shared cache store only the first node will be able to activate
the entry and subsequent nodes will always see null.--
Looking closer the bigger issue is if an entry becomes passivated and then subsequently
written to you will have a different value in the store as you would in memory.
was:Passivation only makes sense with a non shared cache store. The problem is that if
an entry is passivated on a shared cache store only the first node will be able to
activate the entry and subsequent nodes will always see null.
Prevent user from configuring passivation with a shared store
-------------------------------------------------------------
Key: ISPN-7168
URL:
https://issues.jboss.org/browse/ISPN-7168
Project: Infinispan
Issue Type: Bug
Affects Versions: 8.2.4.Final
Reporter: William Burns
Assignee: William Burns
Fix For: 10.0.0.Final
Passivation only makes sense with a non shared cache store. --The problem is that if an
entry is passivated on a shared cache store only the first node will be able to activate
the entry and subsequent nodes will always see null.--
Looking closer the bigger issue is if an entry becomes passivated and then subsequently
written to you will have a different value in the store as you would in memory.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)