[DOCS-13650] Investigate changes in SERVER-47972: maxTimeMS set on hedged requests does not give shards enough time to refresh Created: 15/May/20 Updated: 13/Nov/23 Due: 22/May/20 Resolved: 18/May/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc7, 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Kay Kim (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | docs-sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 38 weeks, 2 days ago | ||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||
| Description |
DescriptionDownstream Change Summary We've increased the default for maxTimeMSForHedgedReads here. Description of Linked TicketGoal: investigate if the scenario outlined below is possible and determine a fix.
Scenario: Suppose shard0 has a primary, secondary0, and secondary1.
In this scenario, we believe secondary0 would be getting killed here. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 18/May/20 ] |
|
Author: {'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |