Skip to content

Rolling deploy should start with any unhealthy hosts #51

Open
@bryannewrelic

Description

@bryannewrelic

Centurion's rolling_deploy action iterates over the hosts: for each, it kills the old container, starts a new one, then waits for the new one to successfully health-check before moving on. With this paradigm, you clearly need to have at least two hosts running something to maintain uptime.... but if the second host is already down for some reason, having only two instances means deploying (or running a migration command) will blindly take your only other instance down.

Rolling deploy (and also anywhere we pick a host to do something on) ought to look for any "down" hosts and deploy to them first.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions