[SERVER-53078] Avoid using streamable RSM in max_time_ms_sharded.js due to maxTimeAlwaysTimeOut failpoint Created: 25/Nov/20 Updated: 29/Oct/23 Resolved: 25/Nov/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Linked BF Score: | 31 | ||||
| Description |
|
The streamable RSM includes a maxAwaitTimeMS in its hello request and the maxTimeAlwaysTimeOut failpoint causes the hello request to immediately hits its deadline. This leads the mongos to not know the replica set member state of the shards. |
| Comments |
| Comment by Githook User [ 25/Nov/20 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: |