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
{{ message }}
This repository was archived by the owner on Feb 18, 2025. It is now read-only.
I have a orchestrator running for the production which have multiple cluster, yesterday one of the master in a particular cluster got failed but orchestrator did not promoted candidate master to a new maser (failover failed), when I started debugging I found INFO topology_recovery: Failure: no replica promoted.. in the logs.
funcIsBannedFromBeingCandidateReplica(replica*Instance) bool {
ifreplica.PromotionRule==MustNotPromoteRule {
log.Debugf("instance %+v is banned because of promotion rule", replica.Key)
returntrue
}
for_, filter:=rangeconfig.Config.PromotionIgnoreHostnameFilters {
ifmatched, _:=regexp.MatchString(filter, replica.Key.Hostname); matched {
returntrue
}
}
returnfalse
}
The above function is returning true when 10.2.9.67 is being compared in PromotionIgnoreHostnameFilters list due to 10.2.9.6 and 10.2.9.167 therefore promotion is not happening.