-
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
Nomad running more services than desired task count #3198
Comments
@ummecasino Can you grab the output of |
i haven't gone through the details of the reported issue, but sometimes I see two dockers running instead of one (for any of my services). When I reboot my compute machine, the number of Dockers is back to their expected count. Shantanu |
@dadgar Sorry, I had to redeploy the service because it's in our QA environment, the evaluation and allocation for the concerning have already been garbage collected. (btw. is there something like a best practice to archive allocations for later analysis?) @shantanugadgil I don't think that this caused the problem, we had no updates etc. in the meantime |
@ummecasino No worries, I am fairly confident that I have the fix for what you hit based on a report from another user. What makes me confident is the time stamps that the two allocs were made at are the same and the fact that they are from separate evaluations. I would grab the relevant allocations and evals using the commands I showed. Often what it requires to debug is different per issue but those + server/client logs in debug are the best bet. |
This PR fixes a scheduling race condition in which the plan results from one invocation of the scheduler were not being considered by the next since the Worker was not waiting for the correct index. Fixes #3198
This PR fixes a scheduling race condition in which the plan results from one invocation of the scheduler were not being considered by the next since the Worker was not waiting for the correct index. Fixes #3198
This PR fixes a scheduling race condition in which the plan results from one invocation of the scheduler were not being considered by the next since the Worker was not waiting for the correct index. Fixes #3198
This PR fixes a scheduling race condition in which the plan results from one invocation of the scheduler were not being considered by the next since the Worker was not waiting for the correct index. Fixes #3198
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: 0.6.0
I'm not shure if this is a possible issue or just a question for which I need clarification: We have returning problems with the count of actual deployed services versus the desired count in the job description.
The following service is actually running with 2 instances, the desired count is 1. I try to give all the information can gather, I'll append the job file.
job.txt
The text was updated successfully, but these errors were encountered: