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

Maintenance mode #1086

Merged
merged 2 commits into from
Jun 9, 2017
Merged

Maintenance mode #1086

merged 2 commits into from
Jun 9, 2017

Conversation

ejholmes
Copy link
Contributor

@ejholmes ejholmes commented Jun 1, 2017

This adds support for putting applications into "maintenance mode", which can be useful for doing things that might require complete downtime, like DB upgrades.

You can put an application into maintenance mode using the emp maintenance-enable command, which masks the scale of all processes to 0. You can then disable maintenance mode with emp maintenance-disable, which unmasks the scale and returns everything back to normal.

Copy link
Contributor

@phobologic phobologic left a comment

Choose a reason for hiding this comment

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

minor comments, looks good

Long: `
Maintenance shows the current maintenance mode state of an app.
Example:
$ emp maintenance
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe show that you should use -a in these docs.

},
{
"scale -l -a acme-inc",
"rake=0:1X scheduled=0:1X web=2:1X worker=0:1X",
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we have some indication here that the stack is in maintenance mode so people aren't confused?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I kinda waffled on that a bit. My current feeling is that this shouldn't change, since it would be a breaking change for scripts. We could return something like rake=0:1X scheduler=0:1X web=0:1X worker=0:1X, but then that's not entirely true, because web is still scaled to 2 in the release.

@ejholmes ejholmes force-pushed the maintenance branch 5 times, most recently from 8678601 to a01382a Compare June 9, 2017 17:07
@ejholmes ejholmes merged commit df1b2bd into master Jun 9, 2017
@ejholmes ejholmes deleted the maintenance branch June 9, 2017 17:58
@ejholmes ejholmes mentioned this pull request Sep 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants