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

docs: always use -ignore-system on node drain with CSI #8606

Merged
merged 1 commit into from
Aug 7, 2020

Conversation

tgross
Copy link
Member

@tgross tgross commented Aug 7, 2020

Postrun hooks for allocation runners don't currently block the registration of
terminal health with the servers, which is what allows system jobs to be
drained. So draining nodes with jobs that claim CSI volumes requires the
-ignore-system job to ensure that the postrun hook for service jobs gets a
chance to execute.

This docs change is associated with #8580 inasmuch as that PR can't fully solve the node drain issue summarized in #8232 (comment)

Postrun hooks for allocation runners don't currently block the registration of
terminal health with the servers, which is what allows system jobs to be
drained. So draining nodes with jobs that claim CSI volumes requires the
`-ignore-system` job to ensure that the postrun hook for service jobs gets a
chance to execute.
@tgross tgross merged commit 1350413 into master Aug 7, 2020
@tgross tgross deleted the docs-csi-node-drain branch August 7, 2020 15:22
@tgross tgross added this to the 0.12.2 milestone Aug 7, 2020
@@ -65,8 +67,10 @@ operation is desired.
- `-no-deadline`: No deadline allows the allocations to drain off the node
without being force stopped after a certain deadline.

- `-ignore-system`: Ignore system allows the drain to complete without stopping
system job allocations. By default system jobs are stopped last.
- `-ignore-system`: Ignore system allows the drain to complete without
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tgross I kinda wish this flag was default "on", I've yet had a case where I haven't had to set this to true in my various nomad deployments

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I agree. Let me float that by the rest of the team to see if it's something we feel safe flipping before 1.0.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've opened #8622 for further discussion of that default. Thanks for raising it, @jippi!

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, 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 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants