[SERVER-46234] Remove the code for computing hedging delay and add maxTimeMSForHedgedReads serverParameter Created: 18/Feb/20 Updated: 29/Oct/23 Resolved: 19/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Service Arch 2020-02-24 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We recently made a few changes to the design. We now always hedge, immediately, and set a maxTimeMS on the hedged read (configurable via maxTimeMSForHedgedReads runtime server parameter). Therefore, the code for staggering support should be removed. That includes the code for the "delay" flag in $readPreference and the code for computing the hedging delay. So the user-facing syntax is now:
|
| Comments |
| Comment by Githook User [ 19/Feb/20 ] |
|
Author: {'username': 'cheahuychou', 'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com'}Message: |