[JBoss JIRA] Created: (JGRP-1336) GMS: if a member leaving takes a long time, it can get merged back into the cluster
4:15 a.m.
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.1
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
9:41 a.m.
New subject: [JBoss JIRA] Updated: (JGRP-1336) GMS: if a member leaving takes a long time, it can get merged back into the cluster
[
https://issues.jboss.org/browse/JGRP-1336?page=com.atlassian.jira.plugin....
]
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
6:38 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1336) GMS: if a member leaving takes a long time, it can get merged back into the cluster
[
https://issues.jboss.org/browse/JGRP-1336?page=com.atlassian.jira.plugin....
]
Galder Zamarreño commented on JGRP-1336:
----------------------------------------
Bela, can you make sure this is solved in next CR? We have a workaround in TEST_PING for
this, but it'd be better to go with your fix.
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
4:38 a.m.
New subject: [JBoss JIRA] Commented: (JGRP-1336) GMS: if a member leaving takes a long time, it can get merged back into the cluster
[
https://issues.jboss.org/browse/JGRP-1336?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1336:
--------------------------------
Solution: add an is_leaving flag to Discovery. Set it to true when leaving and false when
connecting. When true, discard any discovery requests (and responses).
I have no test case for this as it is an edge case and usually won't occur
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
5:02 a.m.
New subject: [JBoss JIRA] Resolved: (JGRP-1336) GMS: if a member leaving takes a long time, it can get merged back into the cluster
[
https://issues.jboss.org/browse/JGRP-1336?page=com.atlassian.jira.plugin....
]
Bela Ban resolved JGRP-1336.
----------------------------
Resolution: Done
Fixed according to solution
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
4790
days inactive
4887
days old
4 comments
2 participants
participants (2)
-
Bela Ban (JIRA) -
Galder Zamarreño (JIRA)