Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
ALL
-
-
Storage NYC 2018-03-26, Storage NYC 2018-04-09
Description
The design of our batch oplog application on secondaries allows temporary intra-batch uniqueness violations for secondary unique indexes. The parallel batch writer mode ensures that readers reading from secondaries cannot observe this state. We need additional testing to stress these protections, so that we can work on removing the need for a parallel batch writer mode and use the timestamp of the last applied batch or command as read timestamp instead..
The test should test the following:
- adding / dropping indexes does not result in secondaries trying to use an index that is not yet ready at the read timestamp
- secondary reads cannot observe invalid intermediate states