Skip to content

Conversation

ayoung
Copy link
Contributor

@ayoung ayoung commented Oct 21, 2016

This pull is intended to fix issue #2346.

I noticed that if a cluster member is in Joining state when you call cluster.Leave(), the member will appear unreachable to other nodes indefinitely. This adds a check to see if the state is Joining, then call Downing() instead.

The only caveat to this is that if you have a callback waiting on cluster.RegisterOnMemberRemoved(someAction) then this won't be called. Is there some other event that should be hooked into for this?

@Aaronontheweb
Copy link
Member

Wondering how we can test this to ensure that it works....

@Danthar
Copy link
Member

Danthar commented Jan 11, 2017

Status on this one? The change itself looks good. @Aaronontheweb

@Aaronontheweb
Copy link
Member

I think this one still needs a spec to verify that its behavior is inline with the cluster specifications

@Aaronontheweb Aaronontheweb self-assigned this Feb 1, 2018
@Aaronontheweb Aaronontheweb added this to the 1.3.5 milestone Feb 1, 2018
@marcpiechura marcpiechura modified the milestones: 1.3.5, 1.3.6 Mar 5, 2018
@Aaronontheweb Aaronontheweb modified the milestones: 1.3.6, 1.3.7 Apr 19, 2018
@Aaronontheweb Aaronontheweb modified the milestones: 1.3.7, 1.3.8 May 15, 2018
@marcpiechura marcpiechura modified the milestones: 1.3.8, 1.3.9 Jun 5, 2018
@Aaronontheweb
Copy link
Member

resolved via #3551

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants