Description
This is related to another bug SOLR-13410
For a solrcloud setup with more than one designated overseer nodes, If we bring down one overseer node, there will be at least one transition overseer node before another designated node assumes overseer role. This is happening because OverseerNodePrioritizer is triggered once we have a new overseer node upon stopping a designated overseer leader node.
Refer to 2 designated overseer nodes test case in testDesignatedOverseerRestarts#OverseerRolesTest in the patch to reproduce this.