[
http://jira.jboss.com/jira/browse/JGRP-203?page=comments#action_12373306 ]
Bela Ban commented on JGRP-203:
-------------------------------
I don't see why PRIMARY_PARTITION needs to sort the MergeView is receives: a MergeView
is only created by the *merge leader*, and therefore it will be exactly the same on all
merge cordinators.
So we don't need to sort it.
A much simpler implementation could be to deterministically find out the primary partition
and then send EXIT events to all members in non-primary partitions.
Even simpler: there could be an option in JChannel that triggers an EXIT if we're not
in the primary partition on reception of a MergeView. User code could be called to
determine the primary partition
Primary Partiton approach for handling of partitions
----------------------------------------------------
Key: JGRP-203
URL:
http://jira.jboss.com/jira/browse/JGRP-203
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6
Attachments: PRIMARY_PARTITION.java
Add this approach to JGroups. Members in a non-primary partition will shut down, become
read-only etc.
Google for "primary partition AND group communication" for the relevant
literature on this
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira