-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Zombie service registered if Service name is changed #658
Comments
@cleung2010 This will be fixed in 0.3 |
I see we keep registering the service once it's name changes infinitely but we do remove the old service. So not sure why you are seeing a zombie service, we know the problem but taking some time to handle updates to allocations in a nicer way. |
It seems that when I delete a job, the services on that job do not get deregistered. Don't know if this should be a separate issue. Edit: Wrong API call on my part on this one, please disregard. |
@cleung2010 Can you post your job description for that? I can't reproduce. |
@diptanu regarding the job deletion? That's a mistake on my part, it's working as intended. |
@cleung2010 Yeah I was asking about the job deletion. We know what's happening when the service name changes, a fix will land soon. Taking some time to handle updates properly. |
@diptanu by zombie service I meant the state of the service registration and not the actual service (that service does get removed/replaced). |
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. |
I encountered an issue where a Task was registered to Consul as service under a specific name, but after changing the name the old task name was still registered, in addition to the new one.
Initially I had this JSON Service object in the job spec:
Running this job registered the
helloworld.service.dc1.consul
service. I then changed the service name to be the following:This registered
nomad-helloworld.service.dc1.consul
, buthelloworld.service.dc1.consul
was also still registered.The text was updated successfully, but these errors were encountered: