[SERVER-52657] index_commands_shard_targeting.js relies on too short MaxTimeMs Created: 06/Nov/20 Updated: 29/Oct/23 Resolved: 10/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.4.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.4, v4.2, v4.0
|
||||||||
| Steps To Reproduce: | Reduce this maxTimeMs to something small like 10ms. |
||||||||
| Participants: | |||||||||
| Linked BF Score: | 17 | ||||||||
| Description |
|
index_commands_shard_targeting.js runs index related commands with a maxTimeMs of 500ms and expects the following two things to happen:
This works most of the time, but on slow variants it can happen that those requests reach their maxTimeMs at an earlier stage of their execution causing the mongos to cancel the request. In these cases the commands will still fail with MaxTimeMsExpired [1], but they didn't have the chance to reach the shard so [2] won't be fulfilled. |
| Comments |
| Comment by Githook User [ 02/Jul/21 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |
| Comment by Githook User [ 10/Dec/20 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |