[jboss-jira] [JBoss JIRA] (JGRP-1379) Make merging more scalable / robust

[ https://issues.jboss.org/browse/JGRP-1379?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1379: --------------------------- Description: Make the MERGE2/GMS/Merger code more robust and scale better in large clusters. - While a merge is going on, stop sending out discovery requests. This reduces unnecessary traffic, especially in large clusters where discovery responses include the entire view of a sub-cluster - If we start a merge, or receive a MERGE-REQUEST, start a timer which cancels the merge after <merge_timeout *2> milliseconds. This is similar to the MergeKiller code, and prevents stale merges, e.g. by a crashed merge leader - If we have merge participants A,B,C,D,E but A only receives merge responses from itself, B and D, then don't cancel the merge, but instead proceed with merging A, B and D. This is currently not done, but a merge is cancelled when we don't get responses from every participant. was: Make the MERGE2/GMS/Merger code more robust and scale better in large clusters. - While a merge is going on, stop sending out discovery requests. This reduces unnecessary traffic, especially in large clusters where discovery responses include the entire view of a sub-cluster - If we start a merge, or receive a MERGE-REQUEST, start a timer which cancels the merge after <merge_timeout *2> milliseconds. This is similar to the MergeKiller code, and prevents stale merges, e.g. by a crashed merge leader - Instead of cancelling a merge on reception of a MERGE_REJECTED response from P, simply exclude P from the merge. This way, we'll have fewer merge cancellations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira