SERVER-133475Needs Scheduling
Ensure priority takeover does not lead to rollback
In a recent help ticket we saw an occurrence of SERVER-118902 triggered by a priority takeover. SERVER-118902 is a known bug where nodes can accept a write for term T after voting in term T+1 but before it selects a sync source that knows about T+1. If these writes need to be rolled back, then it can result in a scenario where a majority of nodes are in the ROLLBACK state, leading to a loss of write availability. Step-down and failover make this unlikely or impossible by ensuring we do not