[SERVER-68704] Clarify the semantics of failing hedged operations Created: 10/Aug/22 Updated: 05/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Participants: | |||||||||
| Description |
|
The goal here is to devise a list of error codes that must be ignored on hedged operations. For example, a hedged operation may fail due to MaxTimeMSExpired, and that doesn't fail the original operation so long as any of the remote commands succeed. We should compile any other error codes that must be treated similarly into a list, and modify the implementation of hedged reads to honor this list. |