-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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.
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
recurring log "serf: attempting reconnect" to left server #3361
Comments
I'm having the same issues. We're also using ASG and the nodes are attemptiong to connect to all the servers that have "left" the cluster. |
@danilobuerger hey as a side note, i'm curious about the |
I don't know if it's needed. |
|
@webengineer it does not. |
This should be fixed by #3611. |
@slackpad Nope. I just tried with consul 1.0.2, same problem. Logs keep on coming, force-leaving them as suggested by the CHANGELOG doesn't work either. |
Same issue with 1.0.3. |
1.0.3 - reconnect attempts went away after force-leave (still there for many hours) and OS-level restart of the server's process (immediately gone) |
|
|
I have the same issue here: version |
Still seeing this issue in edit: running
and now life is happy again. |
We are seeing same issue on version 1.2.2. |
Seeing this on 1.5.1 when I use -retry-join with ASG. Stopping and starting consul on the server fixes the attempting reconnect error. |
consul version
Server:
0.9.0
consul info
Server:
Operating system and Environment details
Amazon AMI 2017.03.1
Description of the Issue (and unexpected/desired result)
consul members
:I am seeing recurring logs of:
However, the server has left.
Reproduction steps
I have a AWS Autoscaling Group (Desired Count 3) with the following consul config:
I then increase the desired count to 4 and then back to 3. After that the then terminated consul server has left the cluster but the logs "serf: attempting reconnect" keep coming.
The text was updated successfully, but these errors were encountered: