[
https://issues.jboss.org/browse/ISPN-9332?page=com.atlassian.jira.plugin....
]
William Burns commented on ISPN-9332:
-------------------------------------
Well while adding tests for this, I found 2 other bugs besides this one.
1. Async cache loader doesn't pay attention to values written right after a clear -
unless a new State is persisted.
2. Async cache loader doesn't properly filter segment entries from modification map.
REPL local iteration optimization cannot be used when store has write
behind
----------------------------------------------------------------------------
Key: ISPN-9332
URL:
https://issues.jboss.org/browse/ISPN-9332
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores, Streams
Affects Versions: 9.3.0.Final
Reporter: William Burns
Assignee: William Burns
When write behind is enabled, the write modification is stored on the primary owner. REPL
local iteration can read from non owned data, thus causing an inconsistency.
Thus distributed streams should always go remote when not all segments are primarily
owned on a given node when write behind is enabled.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)