Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Server agent restarted as client agent does not get removed from peer set #1144

Closed
armon opened this issue Jul 30, 2015 · 1 comment
Closed

Server agent restarted as client agent does not get removed from peer set #1144

armon opened this issue Jul 30, 2015 · 1 comment
Labels
theme/internal-cleanup Used to identify tech debt, testing improvements, code refactoring, and non-impactful optimization type/bug Feature does not function as expected

Comments

@armon
Copy link
Member

armon commented Jul 30, 2015

Current if an agent joins as a server it will be added to the replication group automatically. If it is restarted as a client, it is not removed and could cause availability issues.
@armon armon added the type/bug Feature does not function as expected label Jul 30, 2015
@slackpad slackpad mentioned this issue Aug 4, 2015
Closed
@slackpad slackpad added this to the 0.7.4 milestone Nov 22, 2016
@slackpad slackpad removed this from the Triaged milestone Apr 18, 2017
@slackpad slackpad added the theme/internal-cleanup Used to identify tech debt, testing improvements, code refactoring, and non-impactful optimization label May 25, 2017
@hanshasselberg
Copy link
Member

I started a cluster with 3 servers, killed one of them and restarted as a client:

$ consul operator raft list-peers
Node  ID                                    Address          State     Voter  RaftProtocol
s1    a374994d-1689-141a-b166-10fcf3b57719  127.0.0.1:8101   leader    true   3
s3    5f701d85-a91d-318a-7fbc-2c4e738a8200  127.0.0.1:10006  follower  true   3

s2 was in this list before, but no longer is. As far as I understand, this bug is solved.

@ekmixon ekmixon mentioned this issue Nov 4, 2023
Open
@ekmixon ekmixon mentioned this issue Dec 1, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
theme/internal-cleanup Used to identify tech debt, testing improvements, code refactoring, and non-impactful optimization type/bug Feature does not function as expected
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hanshasselberg @armon @slackpad