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

Failed/paused deployments do not block migrations #4659

Merged
merged 1 commit into from
Sep 11, 2018

Commits on Sep 10, 2018

  1. Failed/paused deployments do not block migrations

    This PR changes behavior of the scheduler such that a task group with a
    deployment that is failed or paused will not cause the scheduler to skip
    migrations.
    
    The reason for this change is that it causes a bad UX when draining
    nodes with allocations that are part of a failed/paused deployment.
    These operations should not be coupled in any way and this remedies
    that.
    
    Prior behavior was still correct, but required either jobs to
    transistion to a healthy state or for the node to hit its drain
    deadline.
    dadgar committed Sep 10, 2018
    Configuration menu
    Copy the full SHA
    14b65c3 View commit details
    Browse the repository at this point in the history