[jboss-jira] [JBoss JIRA] (JGRP-1484) SEQUENCER and merge-views broken

[ https://issues.jboss.org/browse/JGRP-1484?page=com.atlassian.jira.plugin.... ] David Hotham edited comment on JGRP-1484 at 9/4/12 7:46 AM: ------------------------------------------------------------ I wonder if we're having terminology confusion. You say "usually, we have only a few merge coordinators, but many participants". But I think that usually we have only a few coordinators, and (if all is well) even fewer participants. To be clear, by participant I mean a member who has reported himself to the merge leader; but for whom no coordinator claims responsibility. Eg if A, B, C report {A,B}, {A, B}, {A, B, C} then C is a participant because his supposed coordinator A does not have C in view. Then I'm proposing that the merge leader sends INSTALL_MERGE_VIEW * to A, who broadcasts the new view to A and B * to C, who installs it directly (whereas today C will attempt to broadcast the new view to A,B,C - which I claim is pointless). was (Author: dimbleby): I wonder if we're having terminology confusion. You say "usually, we have only a few merge coordinators, but many participants". But I think that usually we have only a few coordinators, and (if all is well) even fewer participants. To be clear, by participant I mean a member who has reported himself to the merge leader; but for whom no coordinator claims responsibility. Eg if A, B, C report {A,B}, {A, B}, {A, B, C} then C is a participant because his supposed coordinator A does not have C in view. Then I'm proposing that the merge leader sends INSTALL_MERGE_VIEW * to A, who broadcasts it to A and B * to C, who installs it directly (whereas today C will attempt to broadcast this to A,B,C - which I claim is pointless). -- 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