3 ms·
Restarting the service and redeploying it should be absolutely the last resort and aren't really sound advice, mainly, because you are losing the invaluable cra
by scarface74 7y ago
Restarting the service and redeploying it should be absolutely the last resort and aren't really sound advice, mainly, because you are losing the invaluable crashed
I’m speaking in terms of AWS translate to your chosen infrastructure.
At the bare minimum you should have two redundant servers behind an autoscaling group with a min/max of two with health checks.
When you need to get something up now and you want to keep the crash state, configure the crash instance to be taken out the autoscaling group but not terminate and start up a new instance. You can then troubleshoot.
- somesomesome 7y ago[deleted]
- scarface74 7y agoIf you’re a solo developer, why would you have something as complicated as k8s? I’m referring to dead simple VMs.