[SERVER-63751] Error when a sleep is added to AsyncResultsMerger::_processBatchResults Created: 16/Feb/22 Updated: 27/Oct/23 Resolved: 10/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jennifer Peshansky (Inactive) | Assignee: | Jennifer Peshansky (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | QE 2022-03-21 |
| Participants: |
| Description |
|
With this diff:
several tests fail with the error: This only happens in the change_streams_per_shard_cursors_passthrough suite. The failing tests are: Filing this ticket to investigate the root cause. |
| Comments |
| Comment by Jennifer Peshansky (Inactive) [ 10/Mar/22 ] | |
|
This doesn't reproduce anymore, now that all the other bug fixes are in. Here's an evergreen patch running this repro against current master. Closing this ticket as "gone away." | |
| Comment by Mickey Winters [ 28/Feb/22 ] | |
|
long story short I confirmed what bernard said and if there is a long enough delay (over 30s ish) between mongos sending a getmore and it actually getting a response, mongos will return NetworkInterfaceExceededTimeLimit to a driver. so that's not a problem, but it doesn't explain there error this ticket saw which is a delay happening internally on mongos | |
| Comment by Mickey Winters [ 28/Feb/22 ] | |
|
ah, I found a bug in the code I pasted above. I am turning off the fail point on mongos when it was turned on on mongod | |
| Comment by Mickey Winters [ 24/Feb/22 ] | |
simulating delay on mongod side |