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

scheduler: datacenter updates should be destructive #10864

Merged
merged 1 commit into from
Jul 14, 2021

Conversation

tgross
Copy link
Member

@tgross tgross commented Jul 7, 2021

Fixes #10746

Updates to the datacenter field should be destructive for any allocation that
is on a node no longer in the list of datacenters, but inplace for any
allocation on a node that is still in the list. Add a check for this change to
the system and generic schedulers after we've checked the task definition for
updates and obtained the node for each current allocation.

@tgross tgross requested review from schmichael and notnoop July 7, 2021 15:17
Updates to the datacenter field should be destructive for any allocation that
is on a node no longer in the list of datacenters, but inplace for any
allocation on a node that is still in the list. Add a check for this change to
the system and generic schedulers after we've checked the task definition for
updates and obtained the node for each current allocation.
Comment on lines +704 to +707
// The alloc is on a node that's now in an ineligible DC
if !helper.SliceStringContains(job.Datacenters, node.Datacenter) {
continue
}
Copy link
Member Author

Choose a reason for hiding this comment

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

As I noted in #10746 (comment) I'm not wild about the placement of this check, because it means we can't really test the behavior except in the whole-scheduler tests as I've done in TestServiceSched_JobModify_Datacenters

Copy link
Contributor

@notnoop notnoop left a comment

Choose a reason for hiding this comment

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

LGTM.

@notnoop notnoop merged commit 6c6a364 into main Jul 14, 2021
@notnoop notnoop deleted the b-10746-plan-datacenter branch July 14, 2021 21:25
@notnoop notnoop mentioned this pull request Jul 28, 2021
notnoop pushed a commit that referenced this pull request Jul 28, 2021
scheduler: datacenter updates should be destructive
notnoop pushed a commit that referenced this pull request Jul 29, 2021
scheduler: datacenter updates should be destructive
@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 Nov 15, 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.

Nomad performs in-place updates when datacenter is changed.
3 participants