Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Query Execution
Description
We don't currently have an easy way to test scenarios where multiple change events have the same clusterTime on different shards. We should add either a unit test to simulate this, or some way to do it in JS integration tests. The latter would probably require a failpoint or similar to exercise control over the oplog timestamps generated on each shard.