[SERVER-82332] Create harness for testing change events at same clusterTime on different shards Created: 19/Oct/23 Updated: 22/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Romans Kasperovics | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query Execution
|
| Participants: |
| 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. |