-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Registering stale services with Consul #5824
Comments
We are hitting this in 0.9.1 as well. |
I believe that should be fixed on #5821 as suggested above. |
Thanks @endocrimes! Will update now and report back 👍 |
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍 |
Apologies for forgetting to reply, for anyone else that finds this can confirm upgrading resolved the issue |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Nomad v0.9.2 (0283266)
(seen on 0.9.0+)
Operating system and Environment details
Amazon Linux 2
Issue
Nomad is registering services with Consul for old allocations
I have a 3-node Nomad server cluster with 2 Nomad agents, all on separate machines. One of the Nomad agents regularly registers services for previous allocations, resulting in a list of registered services failing health checks.
I've tried using the Consul HTTP API to manually deregister the services but they keep coming back.
Nomad:
Screenshot 2019-06-12 at 17 01 52
Consul:
Screenshot 2019-06-12 at 17 02 06
Reproduction steps
Unsure, doesn't seem to happen consistently but has only started since I upgraded from 0.8.6 to 0.9.0 (and then on to 0.9.2)
Let me know what logs/jobspec etc would be helpful and I can share.
The text was updated successfully, but these errors were encountered: