[
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]
Technical notes:
This bug appeared only once, with version 6.0.0.ER4. A new node joined an existing
cluster, but before state transfer ended it split into a separate network partition and
logged a SuspectException. The existing nodes did not receive a new JGroups view for 10
minutes, after which state transfer failed. The cluster never formed with all 3 members.
There were two separate problems:
* Because of the SuspectException on the joiner, it was never able to form a cluster by
itself. This was fixed in Infinispan 5.1.4.CR1 with
https://issues.jboss.org/browse/ISPN-1934.
* The other two nodes did not install a new JGroups cluster view for 10 minutes, blocking
state transfer for this time. It is very likely that this was fixed in AS7 7.1.3 with
https://issues.jboss.org/browse/AS7-4933.
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