[SERVER-50340] Make tailable_getmore_batch_size.js more robust Created: 17/Aug/20 Updated: 29/Oct/23 Resolved: 29/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Ian Boros |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | qexec-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 10 | ||||
| Description |
|
This assertion may fail spuriously when run under a passthrough involving mongos. This is because in sharded deployments, tailable+awaitData cursors may return an empty batch if mongos times out waiting to hear from a shard. We should relax this assertion when running through mongos to check that the number of documents expected is returned "soon" rather than in the next batch. |
| Comments |
| Comment by Githook User [ 29/Aug/20 ] |
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'puppyofkosh'}Message: |