[
https://issues.jboss.org/browse/JGRP-592?page=com.atlassian.jira.plugin.s...
]
Bela Ban commented on JGRP-592:
-------------------------------
The new merge policy tries to minimize moving the cordinator around (JGRP-1002). It works
by picking the coordinator of the MergeView as the first elements of the sorted set of all
subview coordinators. If we have {A,B,C}, {M,N,O} and {X,Y,Z}, then the new coordinator
will be either A, M or X, but not any of the other members.
The rest of the subview ordering is left untouched, e.g. if we pick M as new coord, the
MergeView will be {M,A,B,C,N,O,X,Y,Z}.
Pluggable policy for picking coordinator
----------------------------------------
Key: JGRP-592
URL:
https://issues.jboss.org/browse/JGRP-592
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Minor
Fix For: 3.4
Make policy to pick coordinator pluggable. Pick new coordinator after existing
coordinator crashes by calling this policy.
Default policy is to pick the next in line.
Other policies could pick the next in line from a set of pinned coordinator, so certain
members can never become coordinators.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira