[SERVER-66857] Retry `moveChunk` indefinitely when router hits retriable errors Created: 30/May/22 Updated: 29/Oct/23 Resolved: 30/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc8, 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v6.0
|
||||||||
| Sprint: | Sharding EMEA 2022-06-13 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 163 | ||||||||
| Description |
|
Before v6.0, moveChunk operations issued by users where ending up calling into the configsvr_client that was issuing runCommand with idempotent retry policy, resulting in indefinitely retrying the command in case of retriable errors. With the introduction of the moveRange path, the semantic has been involuntarily changed to a retry with fixed retry attempts both for moveRange and for moveChunk. Purpose of this ticket is to reintroduce the original retry logic.
|
| Comments |
| Comment by Githook User [ 30/May/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |
| Comment by Githook User [ 30/May/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |