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

Bela Ban (JIRA) jira-events at lists.jboss.org
Mon Jul 29 10:04:26 EDT 2013


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

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

Implementing such a policy would be hard:
* The assumption that the first member of a view is the coordinator is a tenet of JGroups as had been in place for a long time
* Therefore, there is a lot of code which depends on this. Locating that code and changing it would be tedious
* Also, a lot of third party code depends on this as well

If we change this, the policy would therefore need to handle both the regular view change and a merge view change, but in both cases, the coordinator needs to be the first of the new view.
                
> 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