Rolling deployments sequence

12

In practice, I have seen the default as canary + immediate.

This is what happens:

  1. Canary boots, health checks pass
  2. Canary gets promoted, replacing old instance #1
  3. Old instance #2 stops
  4. Old instance #3 stops
  5. New instance #2 starts
  6. New instance #3 starts

After first instance boots up, rest of the instances shut down together like this:

2021-12-27T05:55:15.088 app[0e49f967] mia [info] Star child exited with signal (with signal 'SIGINT', core dumped? false)
2021-12-27T05:55:15.088 app[0e49f967] mia [info] Starting clean up.
2021-12-27T05:55:15.158 app[d9752c87] dfw [info] Main child exited with signal (with signal 'SIGINT', core dumped? false)
2021-12-27T05:55:15.158 app[d9752c87] dfw [info] Starting clean up.
2021-12-27T05:55:15.241 app[0eefd5ed] mad [info] Main child exited with signal (with signal 'SIGINT', core dumped? false)
2021-12-27T05:55:15.242 app[0eefd5ed] mad [info] Starting clean up.

This is a bug?

1 Like