[jboss-jira] [JBoss JIRA] Updated: (JGRP-1336) GMS: if a member leaving takes a long time, it can get merged back into the cluster
Bela Ban (JIRA)
jira-events at lists.jboss.org
Mon Sep 19 10:41:26 EDT 2011
[ https://issues.jboss.org/browse/JGRP-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bela Ban updated JGRP-1336:
---------------------------
Fix Version/s: 3.0
(was: 3.1)
> GMS: if a member leaving takes a long time, it can get merged back into the cluster
> -----------------------------------------------------------------------------------
>
> Key: JGRP-1336
> URL: https://issues.jboss.org/browse/JGRP-1336
> Project: JGroups
> Issue Type: Bug
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.0
>
>
> When JChannel.disconnect() is called, and the leave processing takes a long time (e.g. due to excessive CPU use and GC), then it can happen that the leaving node is merged back into the cluster.
> This occurred in the Infinispan testsuite which is run in parallel (high CPU contention).
> SOLUTION: after sending the LEAVE request, disable discovery, so MERGE2 won't discover us.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list