]
Manik Surtani updated JBCACHE-1076:
-----------------------------------
Fix Version/s: 3.2.0
(was: 3.0.0.GA)
Priority: Minor (was: Major)
I see this as an edge case since it could lead to data inconsistencies anyway (same as
async repl) but with none of the perf advantages.
REPL_SYNC only waits for the majority of responses (not all)
------------------------------------------------------------
Key: JBCACHE-1076
URL:
https://jira.jboss.org/jira/browse/JBCACHE-1076
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Bela Ban
Assignee: Manik Surtani
Priority: Minor
Fix For: 3.2.0
By default, synchronous replication has to wait for *all* acks (whereas asynchronous repl
waits for none). We should be able to define a config option, where we only wait for a
majority of responses. For example, if we have a cluster of 10 nodes, and we don't
want to wait for 10 acks, we could define that all sync method calls return after having
received 6 acks.
Advantage: if we have 1-2 slow nodes in the above example, and have to wait for all
replies, we are slowed down by a minority.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: