[DOCS-3461] Clearer documentation about shard migration steps Created: 23/May/14  Updated: 30/Oct/23  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Joanna Cheng Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:
Days since reply: 7 years, 29 weeks ago

 Description   

The point mentioned was the case when the old shard and new shard are in separate networks and no communication between them is possible.

  • You can't iteratively migrate replica set members; you need to force a reconfiguration of the replica set on the new hosts
  • You then need to manually modify the config servers as the mongoS has no idea the hosts backing the shards have changed

Clearer steps on these 2 points are needed



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Generated at Thu Feb 08 07:45:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.