[SERVER-80020] The exhaustiveFindOnConfig() method should retry on NetworkInterfaceExceededTimeLimit errors Created: 15/Aug/23 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nandini Bhartiya | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
In HELP-48617 the ShardRegistry::_lookup() failed with a NetworkInterfaceExceededTimeLimit error. The underlying Shard::exhaustiveFindOnConfig() method retries thrice in case of a Retriable error, but did not in this case because the NetworkInterfaceExceededTimeLimit error does not belong to the Retriable Error category, (it only belongs to the ExceededTimeLimitError,NetworkTimeoutError categories). Since this is an idempotent operation, it should be retried on NetworkInterfaceExceededTimeLimit errors as well. Note: NetworkInterfaceExceededTimeLimit errors will be made retrievable in the future by SERVER-72055. |