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

node drain default behavior for -ignore-system #8622

Open
tgross opened this issue Aug 10, 2020 · 1 comment
Open

node drain default behavior for -ignore-system #8622

tgross opened this issue Aug 10, 2020 · 1 comment

Comments

@tgross
Copy link
Member

tgross commented Aug 10, 2020

In #8606 (comment) @jippi raised the question of whether nomad node drain should have the -ignore-system flag set by default.

Currently the default behavior is that service and batch jobs are drained, and then system jobs are drained. However, internal allocation runner post-run hooks (ex. deregistering from Consul, cleaning up disk) don't block draining the system jobs, so they may run concurrently with the system jobs being drained. With the -ignore-system flag, the system jobs are never drained, which makes them available during shutdown.

The -ignore-system flag appears to be strictly more useful than not having it set. Some example scenarios where you'd want to have a system job that runs until all other workloads have completed:

  • log shippers
  • monitoring agents
  • ingress proxies (ex. Nginx or HAProxy in front of web services)
  • CSI node plugins

Changing the default behavior would break backwards compatibility, so we want to solicit feedback from the community about whether this change would be disruptive.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants