[
https://issues.jboss.org/browse/ISPN-9332?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-9332:
------------------------------------
[~william.burns] going back to the original problem, I would think this an issue only with
shared stores, but your commit goes remote even for non-shared stores if they have
write-behind enabled.
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
Priority: Major
Fix For: 9.4.0.CR3
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.12.1#712002)