[ https://issues.jboss.org/browse/JGRP-592?page=com.atlassian.jira.plugin.s... ] Bela Ban edited comment on JGRP-592 at 7/30/13 6:57 AM: -------------------------------------------------------- The new merge policy tries to minimize moving the cordinator around (JGRP-1002). It works by picking the coordinator of the MergeView as the first elements of the sorted set of all subview coordinators. If we have \{A,B,C\}, \{M,N,O\} and \{X,Y,Z\}, then the new coordinator will be either A, M or X, but not any of the other members. The rest of the subview ordering is left untouched, e.g. if we pick M as new coord, the MergeView will be \{M,A,B,C,N,O,X,Y,Z\}. was (Author: belaban): The new merge policy tries to minimize moving the cordinator around (JGRP-1002). It works by picking the coordinator of the MergeView as the first elements of the sorted set of all subview coordinators. If we have {A,B,C}, {M,N,O} and {X,Y,Z}, then the new coordinator will be either A, M or X, but not any of the other members. The rest of the subview ordering is left untouched, e.g. if we pick M as new coord, the MergeView will be {M,A,B,C,N,O,X,Y,Z}. -- 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