[
https://jira.jboss.org/jira/browse/JGRP-981?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on JGRP-981:
---------------------------------------
A quick theory:
When 2nd instance joins, ClientGmsImpl.installView executes this:
gms.installView(new_view);
gms.becomeParticipant();
gms.passUp(new Event(Event.BECOME_SERVER));
gms.passDown(new Event(Event.BECOME_SERVER));
return true;
Until the gms.becomeParticipant() call returns, a new view coming in to GMS will result in
a call to this in ClientGmsImpl:
public synchronized void handleViewChange(View new_view, Digest digest) {
if(log.isTraceEnabled())
log.trace("view " + new_view.getVid() + " is discarded as we
are not a participant");
}
Result is the view change is discarded.
I haven't verified this; at this point it's a working theory.
Wrong view with concurrent startup
----------------------------------
Key: JGRP-981
URL:
https://jira.jboss.org/jira/browse/JGRP-981
Project: JGroups
Issue Type: Bug
Affects Versions: 2.4.5
Reporter: Dennis Reed
Assignee: Bela Ban
When starting multiple nodes simultaneously, one node sometimes retains an old view.
Other than the obvious issues, this prevents STABLE from working, and NAKACK will
eventually use up the heap.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira