[
https://issues.jboss.org/browse/ISPN-1944?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-1944:
-----------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
806855|https://bugzilla.redhat.com/show_bug.cgi?id=806855]
Dan Berindei <dberinde(a)redhat.com> made a comment on jira ISPN-1944
After examining the logs closer, it seems the SuspectException is only part of the problem
(and it's actually described in ISPN-1934).
At some point node3 suspects both node01 and node03 and excludes them from the view, but
node01 neither removes node03 from its view nor tries to merge the partitions for 10
minutes (see the attached ispn-1944.txt log).
We need to find whether there is anything that we can change in the JGroups configuration
to prevent this kind of situation. Bela suggested using MERGE3 (see ISPN-1951), but
it's not available in JGroups 3.0.8.
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