[
https://issues.jboss.org/browse/ISPN-5042?page=com.atlassian.jira.plugin....
]
Dan Berindei resolved ISPN-5042.
--------------------------------
Resolution: Done
It's no longer relevant, with staggered gets (ISPN-825) we already ask the primary
owner first, and only ask the backups if the primary is too slow.
Remote gets caused by writes could be replicated only to the primary
owner
--------------------------------------------------------------------------
Key: ISPN-5042
URL:
https://issues.jboss.org/browse/ISPN-5042
Project: Infinispan
Issue Type: Enhancement
Components: Core, State Transfer
Affects Versions: 7.1.0.Alpha1
Reporter: Dan Berindei
Assignee: Sebastian Ćaskawiec
Priority: Minor
Labels: 7.0
Fix For: 8.2.0.Final
For write operations that need the previous value, a write CH-only owner that doesn't
have a key locally will attempt to retrieve the key from the read CH-owners.
Sending the remote get command to all the previous owners will create extra load on the
cluster during state transfer, so it should be more efficient to send the remote get only
to the primary owner. Even though the latency of some write operations will be higher, the
average latency should be better.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)