[SERVER-74177] balancer_commands_scheduler wraps retryable error into OperationFailed error, making them not eligible for retry Created: 17/Feb/23  Updated: 18/Dec/23  Resolved: 09/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Silvia Surroca
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-73877 Wait for shard to have a primary befo... Closed
is related to SERVER-76403 Wait for shard to have a primary befo... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-04-17, Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15
Participants:
Linked BF Score: 154

 Description   

For example, we send the moveRange request with retry, but when the moveRange command in the configsvr tries to send the command to the shard and gets an error, it can end up wrapping it with OperationFailed error code making it not eligible for retry



 Comments   
Comment by Githook User [ 08/May/23 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-74177 moveChunk must retry on retryable errors
Branch: master
https://github.com/mongodb/mongo/commit/5bb57d1e1504425d683e47fb0fcd6e523cf94f85

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