[SERVER-56044] [SBE] Fix various $changeStream tests timing out Created: 12/Apr/21 Updated: 06/Dec/22 Resolved: 18/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kyle Suarez | Assignee: | Backlog - Query Execution |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Many tests in the SBE build variant that exercise sharding fail with
A non-exhaustive list of these tests in jstests/sharding/:
This ticket also encompasses assert.soon() failures related to change streams in the multiversion suite:
See also |
| Comments |
| Comment by Githook User [ 19/Apr/21 ] | ||||||||||||
|
Author: {'name': 'Drew Paroski', 'email': 'drew.paroski@mongodb.com', 'username': 'paroski'}Message: | ||||||||||||
| Comment by Drew Paroski [ 18/Apr/21 ] | ||||||||||||
|
I verified that the patch that Arun is working on for I also verified that Arun's patch will fix the multiversion failures listed above: https://spruce.mongodb.com/version/607a792f0305b920702f6d44/tasks Closing this task as a duplicate of | ||||||||||||
| Comment by Drew Paroski [ 17/Apr/21 ] | ||||||||||||
|
I confirmed by bisecting that the diff for I've removed "jstests/sharding/change_streams_establishment_finds_new_shards.js" from the list above. | ||||||||||||
| Comment by Kyle Suarez [ 12/Apr/21 ] | ||||||||||||
|
The error for sharding/change_streams.js doesn't look exactly like the others:
However that line in the test is just asserting we see the first change stream result in a timely manner, like the others:
| ||||||||||||
| Comment by Kyle Suarez [ 12/Apr/21 ] | ||||||||||||
|
The error for js_test:change_stream_enforce_max_time_ms_on_mongos.js looks slightly different but I still believe this is because of a change stream not returning in a timely manner:
|