mirror of https://github.com/zulip/zulip.git
b2d01e2da0
The manual step here is that we need to do the `puppet apply` before pushing this commit, or `restart-server` will crash. Previously we shut down everything in one group, which performed poorly with supervisor's bad performance on restarting many daemons at once. Now we shut down the unimportant stuff, then the important stuff, bring back the important stuff, and then bring back the unimportant stuff. This new model has a little over 5s of downtime for the core user-facing daemons -- which is still far more than would be ideal, but a lot less than the 13s or so that we had before. Here's some logs with the current setup for the tornado/django downtime: 2013-12-19 20:16:51,995 restart-server: Stopping daemons 2013-12-19 20:16:53,461 restart-server: Starting daemons 2013-12-19 20:16:57,146 restart-server: Starting workers Compare with the behavior on master today: 2013-12-19 20:21:45,281 restart-server: Stopping daemons 2013-12-19 20:21:49,225 restart-server: Starting daemons 2013-12-19 20:21:58,463 restart-server: Done! (imported from commit b2c1ba77f3dc989551d0939779208465a8410435) |
||
|---|---|---|
| .. | ||
| lib | ||
| setup | ||
| purge-old-deployments | ||
| restart-server | ||
| upgrade-zulip | ||
| zulip-puppet-apply | ||