[jboss-jira] [JBoss JIRA] (JGRP-592) Pluggable policy for picking coordinator

Bela Ban (JIRA) jira-events at lists.jboss.org
Tue Jul 30 05:36:26 EDT 2013


    [ https://issues.jboss.org/browse/JGRP-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793735#comment-12793735 ] 

Bela Ban commented on JGRP-592:
-------------------------------

Actually, I take the above statement back :-)

We can leave the basic tenet in place: the first element of the membership is always the coordinator ! We only make the way the *membership is computed* pluggable. This needs to be done in 2 places:
* When the coordinator determines the new membership
* When the coordinator is suspected and the next-in-line participant needs to determine whether it will become the new coordinator

We also need to make the computation of the new MergeView in Merger.MergeTask.run() pluggable
                
> 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


More information about the jboss-jira mailing list