[jboss-jira] [JBoss JIRA] Updated: (JGRP-1002) Merge: make the coordinator remain the same if possible after a merge

[Bela Ban (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban updated JGRP-1002:
---------------------------

    Fix Version/s: 3.1
                       (was: 3.0)


> Merge: make the coordinator remain the same if possible after a merge
> ---------------------------------------------------------------------
>
>                 Key: JGRP-1002
>                 URL: https://issues.jboss.org/browse/JGRP-1002
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.1
>
>
> 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

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira