SERVER-132541ClosedWon't Fix

Consider waiting instead of immediately failing snapshot reads if no committed snapshot is available yet

Currently a node that just stepped up as writable primary can [fail \{readConcern: {level: "snapshot"}} reads with a SnapshotUnavailable: "No committed OpTime for snapshot read"|https://github.com/mongodb/mongo/blob/804b9bc48e991a9702c14eab4dd2e9e4d2001312/src/mongo/db/read_concern_mongod.cpp#L404-L406] until it can manage to advance the committed snapshot via the JournalFlusher. This behavior is surprising considering [majority reads|https://github.com/mongodb/mongo/blob/804b9bc48e991a9702c1

Affected Versions
Versions known to exhibit this issue
7.0.08.0.08.2.09.0.0-rc08.3.09.1.0-rc0
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.