[
https://issues.jboss.org/browse/JGRP-592?page=com.atlassian.jira.plugin.s...
]
Bela Ban commented on JGRP-592:
-------------------------------
[Comment from JGRP-1002]
When we have {C, A, B} and split into {C,A} and {B}, then a merge will produce {A,B,C}.
Therefore the coord is moved from C to A. For certain apps, e.g. JBoss singletons, this is
not good, as we're moving the singleton services from a perfectly healthy node to a
different node.
GOAL: come up with a deterministic policy of picking a coord such that we minimize coord
switching if the existing coord is still member of the cluster.
This depends on or is related to the flexible coord pick policy JIRA issue
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.1
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira