If orchestrator is busy and handles more than a few failures then it is useful to be able to filter the failure behaviour by Analysis type.
In my usage I see quite a lot of intermediate master failures DeadIntermediateMaster and a few primary master failures DeadMasterFailure. This is partly a consequence of active server replacement knowing that orchestrator will just handle these failures efficiently and having quite a large fleet of MySQL servers managed by Orchestrator. Currently it is not easy to filter by the appropriate type.
My request would be to add such a filter in addition to the existing filters. Maybe not urgent or needed by others who have few failovers to worry about.
If orchestrator is busy and handles more than a few failures then it is useful to be able to filter the failure behaviour by Analysis type.
In my usage I see quite a lot of intermediate master failures
DeadIntermediateMaster
and a few primary master failuresDeadMasterFailure
. This is partly a consequence of active server replacement knowing that orchestrator will just handle these failures efficiently and having quite a large fleet of MySQL servers managed by Orchestrator. Currently it is not easy to filter by the appropriate type.See: https://github.com/openark/orchestrator/blob/master/go/http/api.go#L3750-L3757
My request would be to add such a filter in addition to the existing filters. Maybe not urgent or needed by others who have few failovers to worry about.