There is an unlikely scenario where two mongod nodes could simultaneously enter primary mode and connect to two open log segments, accepting writes independently. This creates a risk of overlapping writes to both nodes, which could lead to a split history issue.

To mitigate this risk, it is proposed that the current behavior of primary nodes be modified. Specifically, when the primary send heartbeats to all nodes in the shard it could indicate the current term. If a primary receives a heartbeat indicating a larger term from another node, it should step down and relinquish its primary status.

Implementing this behavior would decrease the likelihood of the split history scenario occurring and improve system consistency.