We observed a scenario where a MongoDB node completes an initial sync, but part of the history obtained during the initial sync needs to be rolled back.

In such cases, the node does not have any stable timestamp available for recovery because there is no history before the initial sync completes. As a result, the rollback cannot proceed, leading to a node crash.

We want to investigate if it is possible to detect this situation in advance and provide a clear warning message before crashing. The warning should indicate that the node must redo the initial sync to recover.