[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:
Backports
Depends
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: SERVER-66857 Retry `moveChunk` and `moveRange` indefinitely when router hits retriable errors
Branch: v6.0
https://github.com/mongodb/mongo/commit/6b4d0239a82e8e7375b4ea04103a0e47e40a5bef

Comment by Githook User [ 30/May/22 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-66857 Retry `moveChunk` and `moveRange` indefinitely when router hits retriable errors
Branch: master
https://github.com/mongodb/mongo/commit/89700662ef561bb043615b8bffd4f5316efbea07

Generated at Thu Feb 08 06:06:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.