[SERVER-22935] Add JS/client function to retry moveChunk on mongod stepdown related errors Created: 02/Mar/16  Updated: 06/Dec/22  Resolved: 20/Jul/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-24856 Manual moveChunk requests should go t... Closed
depends on SERVER-24866 Balancer should be able to recover it... Closed
Related
is related to SERVER-22822 Prevent mongod step down during moveC... Closed
Assigned Teams:
Sharding
Participants:

 Description   

If a moveChunk operation fails because one of the mongods involved in the migration (donor or recipient) stepped down, the client should retry the moveChunk operation.

*NOTE*
SERVER-22822 should be reverted whenever the retry moveChunk helper works. The changes prevented mongod step downs rather than retrying the moveChunk operation, and will no longer be necessary when there's a retry.



 Comments   
Comment by Kaloian Manassiev [ 20/Jul/16 ]

This retry functionality will not be necessary once all migrations (both manual and automatic) go through the CSRS primary.

Generated at Thu Feb 08 04:01:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.