-
Type: Improvement
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
In the procedure for restoring a sharded cluster step 5 states:
"If shard hostnames have changed, update the config database.
If shard hostnames have changed, connect a mongo shell to the mongos instance and update the shards collection in the Config Database to reflect the new hostnames."
I believe an example will make this step clear. For example:
Get the current configuration:
use config db.shards.find()
A typical output would be as follows:
{ "_id" : "shard01", "host" : "shard01/oldHost1:27018,oldHost1:27018,oldHost1:27018" }
Finally, updating the document with the new hosts:
db.shards.update({_id:"shard01"},{$set:{"host":"shard01/newHost1:27018,newHost2:27018,newHost3:27018"}})
- is related to
-
DOCS-11486 Missing RS re-configuration in Manual Sharded Cluster restore procedure
- Closed
-
DOCS-11479 Update docs with procedures requiring to restart repl set nodes as stand alone
- Closed
-
DOCS-9517 Docs for SERVER-24465: Remove recoverShardingState parameter
- Closed