The test was previously "fixed" in SERVER-89428 by using causally consistent sessions. The fix was not complete and only made the failure less frequent, because "local" readConcern + "majority" writeConcern doesn't guarantee that read operations reflect the results of write operations that precede them (see the table our documentation).
- is related to
-
SERVER-89428 Use causally consistent sessions in out_merge_on_secondary_batch_write.js
- Closed