[jboss-jira] [JBoss JIRA] Resolved: (JGRP-915) GMS: when coordinator leaves, the new view's creator should be the next member in line, not the current coord

Bela Ban (JIRA) jira-events at lists.jboss.org
Thu Feb 26 11:20:44 EST 2009


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

Bela Ban resolved JGRP-915.
---------------------------

    Resolution: Done


> GMS: when coordinator leaves, the new view's creator should be the next member in line, not the current coord
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JGRP-915
>                 URL: https://jira.jboss.org/jira/browse/JGRP-915
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 2.8
>
>
> If we have {A,B,C} and A is the coordinator, assume the view is {A|10}.
> When A leaves (gracefully), then the new view is {A|11}, but the coord is B. (Note that when A crashes the new view is {B|11}).
> This is correct, but since A left, we'll have no UUID/logical name caching, so the ViewID will not use the logical name to print, but the UUID, which is not nice.
> So we'll change the semantics as follows: in the example above, the new view will be {B|11} both on crash failover (current behavior) *and* on graceful leave of A (new behavior).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list