[
https://issues.jboss.org/browse/JGRP-1705?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1705:
--------------------------------
The merging seems to work fine as Karim achieved a cluster of 1538 nodes:
http://belaban.blogspot.ch/2013/09/new-record-for-large-jgroups-cluster.html.
Made a few more changes:
* When a TMP_VIEW is received, the InfoSender and ViewConsistencyChecker are stopped
(restarted on VIEW)
* When an INFO is received from sender P, we remove P's previous INFO registrations
MERGE3 handles fake merge views
-------------------------------
Key: JGRP-1705
URL:
https://issues.jboss.org/browse/JGRP-1705
Project: JGroups
Issue Type: Bug
Affects Versions: 3.4
Reporter: Karim AMMOUS
Assignee: Bela Ban
Fix For: 3.4
Attachments: JIRA-MERGE-1subGroup-Shutdown.log, JIRA-MERGE-1subGroup.log
Under some conditions, MERGE3 handles fake merge views. After "merge", number
of members that form the cluster still the same and the mergeView contains only one
subgroup.
Scenario:
- Form a large cluster (1115 mbrs)
- Enable MERGE3 TRACE logging level on coordintor member (172.29.190.5)
- Reboot one machine (172.29.190.5) hosting 7 JVMs
- Coord install a new view with 1108 mbrs.
When new members join the cluster we observe a merge view formed by only one subgroup.
Coordinator log file was attached to this JIRA.
--
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