[SERVER-63156] Investigate additional passthrough suites for testing per-shard cursors Created: 31/Jan/22 Updated: 09/Mar/22 Resolved: 09/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Change streams, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mickey Winters | Assignee: | Mickey Winters |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | QE 2022-03-07, QE 2022-03-21 |
| Participants: |
| Description |
|
we should evaluate other passthough/override options to be ran in conjunction with implicit pass through to get even more coverage on per shard cursors. for example jstests/libs/override_methods/implicit_whole_db_changestreams.js |
| Comments |
| Comment by Mickey Winters [ 09/Mar/22 ] |
|
after looking at the sharded change streams tests it doesn't seem like we could easily reuse them with some kind of override. we would have to manually change all of them and adapt them to be suitable for per shard cursors. I tried running the pre shard cursor suite with continuous step downs just to see if it could shake out anything interesting but it was basically green. per shard cursors and normal sharded change streams both use the common AsyncResultsMerger class so I believe we actually have good coverage already on correct sharding behavior, so I will close this ticket. |
| Comment by Mickey Winters [ 28/Feb/22 ] |
|
there are a bunch of whole cluster specific tests in the change_streams suite so i think the current coverage there is probably fine. There are some sharded change stream tests we can try to reuse somehow, perhaps using an override to ShardingTest or something |