On Monday, 29 September 2014 at 19:23:28 UTC, Sean Kelly wrote:
On Monday, 29 September 2014 at 07:52:33 UTC, Paolo Invernizzi
wrote:
On Monday, 29 September 2014 at 04:03:37 UTC, Sean Kelly wrote:
On Monday, 29 September 2014 at 02:57:03 UTC, Walter Bright
Right. But if the condition that caused the restart
persists, the process can end up in a cascading restart
scenario. Simply restarting on error isn't necessarily
enough.
This can be mitigated: a cascade reboot would occur if the
problem affects the reboot sequence itself.
Or if an ongoing situation causes the problem to rapidly
reoccur.
Look at most MMO game launches for example. Production load
hits and some process falls over in a weird way, which increases
load because everyone goes nuts trying to log back in, and when
the system comes back up it immediately falls over again.
Rinse,
repeat.
Is it not better to throttle down the connection volumes before
it reach processes not being able to handle an overload in in a
correct way?
---
/Paolo
