Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No indication of manual recovery (vs automatic recovery) in web/audit-recovery/id/9999 #202

Open
sjmudd opened this issue Apr 25, 2016 · 0 comments

Comments

@sjmudd
Copy link
Contributor

sjmudd commented Apr 25, 2016

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant