You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
orchestrator on detecting a master failure may be configured to recover from the situation or this may need to be done manually. The current logging does not make it clear which action took place (automatic or manual) and for later forensics this information would be most useful.
I have a cluster of orchestrator servers to provide HA and on one of the idle boxes I see the logging:
[martini] Started GET /api/lb-check for a.b.c.d
[martini] Completed 200 OK in 718.939µs
2016-04-24 07:54:52 DEBUG executeCheckAndRecoverFunction: proceeeding with some-host:3306; skipProcesses: false
2016-04-24 07:54:52 DEBUG topology_recovery: will handle DeadMaster event on some-host:3306
2016-04-24 07:54:52 DEBUG auditType:recover-dead-master instance:some-host...
...
There is no indication that this is triggered "manually" by a user (in this case)
If possible it would be most convenient to include:
an indication of whether the failover was triggered by a manual event (triggered by a user), or
triggered as an automatic process from the configuration.
if the username is known then please provide that information.
The text was updated successfully, but these errors were encountered:
orchestrator on detecting a master failure may be configured to recover from the situation or this may need to be done manually. The current logging does not make it clear which action took place (automatic or manual) and for later forensics this information would be most useful.
I have a cluster of orchestrator servers to provide HA and on one of the idle boxes I see the logging:
[martini] Started GET /api/lb-check for a.b.c.d
[martini] Completed 200 OK in 718.939µs
2016-04-24 07:54:52 DEBUG executeCheckAndRecoverFunction: proceeeding with some-host:3306; skipProcesses: false
2016-04-24 07:54:52 DEBUG topology_recovery: will handle DeadMaster event on some-host:3306
2016-04-24 07:54:52 DEBUG auditType:recover-dead-master instance:some-host...
...
There is no indication that this is triggered "manually" by a user (in this case)
If possible it would be most convenient to include:
The text was updated successfully, but these errors were encountered: