As per this comment, it is safe for the resharding donor oplog iterator to briefly read from a secondary with no timestamp.
- is related to
-
SERVER-59775 ReshardingDonorOplogIterator triggers an fassert() when it continues to run in member state SECONDARY following a stepdown
-
- Closed
-
-
SERVER-79399 Remove ShouldNotConflictWithSecondaryBatchApplicationBlock and related functions
-
- Closed
-
- related to
-
SERVER-79955 Need a more complete mechanism for internal readers to avoid fassert when crossing member state PRIMARY to SECONDARY transition
-
- Closed
-