3 ms·
If you seriously want no downtime you should never touch-reload. ALWAYS spin up new infrastructure, smoketest, switch the loadbalancer. You might run into pro
by Beltiras 11y ago
If you seriously want no downtime you should never touch-reload. ALWAYS spin up new infrastructure, smoketest, switch the loadbalancer. You might run into problems with load you didn't see from testing but you can reverse and minimize downtime.
- hackerboos 11y agoThis. I load tested my zero downtime unicorn setup and got a few lost requests during the reload. That said, if you boot a VM and it's bad, you are going to lose requests then too.
- Beltiras 11y agoFirst of all, what is a "bad vm"? Second: smoketests should show if the engine is up and serving requests not under load. Third: you have the fallback of reversing the flow. You will always lose requests. All you can do is minimize the damage. EDIT: Want to clarify what I mean by lose requests since someone is downvoting. In the process of administrating a site with that many requests and a moving infrastructure you can plan as much as you want and try to employ hedging strategies all you want. You will STILL run into problems once in a while that will drop messages. You don't have to lose requests to handing load-balancing off to another handler and you can reload apps without losing requests if the app server is properly coded.