[
https://issues.jboss.org/browse/ISPN-1944?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-1944:
-----------------------------------------------
Dan Berindei <dberinde(a)redhat.com> made a comment on [bug
806855|https://bugzilla.redhat.com/show_bug.cgi?id=806855]
It looks like I was wrong about FD_SOCK, it actually doesn't detect immediately when a
node has left the cluster (and the channel is still up, but seeing only a part of the
cluster).
However, when C leaves the cluster, FD_ALL on C notices that it is the only member and it
stops broadcasting heartbeat messages. After the FD_ALL timeout expires, A and B will
suspect C and eliminate it from their view. So it still shouldn't be possible for A
and B to see view A2 [A, B, C] for 10 minutes after C left...
SuspectedException blocks cluster formation
-------------------------------------------
Key: ISPN-1944
URL:
https://issues.jboss.org/browse/ISPN-1944
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.1.2.FINAL
Reporter: Michal Linhard
Assignee: Dan Berindei
Priority: Critical
Fix For: 5.1.4.CR1
Attachments: ispn-1944.txt
This happened in JDG 6.0.0.ER4.
The cluster with first two nodes formed alright and when node3 was joining, it got
SuspectedException for some reason, and then prepare in node01 failed with timeout
(10min).
logs here:
http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-RESILIENCE/j...
--
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