SERVER-135085Open

Enforce one watermark per checkpoint invariant

In {{{}ReplicatedFastCountManager::initializeMetadata(){}}}, we must check if there is a pre-existing watermark during recovery. If yes, the flusher should not emit another watermark until the flusher persists its first checkpoint. This change is motivated by the pathological case where a node experienced several faults consecutively, emits several watermarks without corresponding checkpoints, and the tailer gets stuck behind. It also simplifies the oplog application logic on standby. See

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.