-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
ALL
-
v5.0
-
Sharding 2021-05-17, Sharding 2021-06-14, Sharding 2021-05-31
Currently we block writes to a tenant's data after reserving the oplog slot that corresponds to the block timestamp. This means a write to the tenant's data can commit with a higher opTime timestamp than the block timestamp, which is at odds with the design. Instead, we should block writes before reserving the oplog slot.