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.

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 node-drain rescheduled all completed periodic tasks #1193

Closed
mitchellh opened this issue May 21, 2016 · 1 comment · Fixed by #1205
Closed

nomad node-drain rescheduled all completed periodic tasks #1193

mitchellh opened this issue May 21, 2016 · 1 comment · Fixed by #1205

Comments

@mitchellh
Copy link
Contributor

Nomad version

0.3.2

Operating system and Environment details

Ubuntu 14.04 LTS (all clients and servers)

Issue

I modified some system settings and brought up a new Nomad client (new instance). I did a nomad drain on the other Nomad client. It immediately scheduled seemingly dozens of periodic tasks that had completed, onto the new node. I can verify based on the logs that they all re-ran.

Reproduction steps

  1. Start a single server, single client
  2. Create a periodic job, let it run for awhile, at least a dozen times
  3. Start a second client, no allocations go to it (they're all happy on the first client)
  4. Drain the first client, run nomad node-status on the new client, see all periodic tasks re-enter "pending" state with desired state "run"
@github-actions
Copy link

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants