[DOCS-9517] Docs for SERVER-24465: Remove recoverShardingState parameter Created: 05/Dec/16  Updated: 30/Oct/23  Resolved: 12/Apr/19

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

Type: Task Priority: Major - P3
Reporter: Emily Hall Assignee: Ravind Kumar (Inactive)
Resolution: Done Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
documents SERVER-24465 Remove recoverShardingState parameter Closed
Related
related to DOCS-12315 Update restore procedure Closed
related to DOCS-11648 Unclear step in restoring a sharded c... Closed
Participants:
Days since reply: 4 years, 41 weeks, 1 day ago

 Description   

Engineering Ticket Description:

And make sure that there will be no shard recovery if mongod started without --shardsvr

 

Please update https://docs.mongodb.com/manual/tutorial/restore-sharded-cluster/index.html, step 6.1.



 Comments   
Comment by Githook User [ 30/Apr/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-9517,DOCSP-4513: rm recoverShardingState parameter
Branch: v4.0
https://github.com/mongodb/docs/commit/ce9d076f9e65c0400fb8cc59e993b242567a0e03

Comment by Githook User [ 30/Apr/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-9517,DOCSP-4513: rm recoverShardingState parameter
Branch: master
https://github.com/mongodb/docs/commit/3c6195858aae9795cfefbe13c4b66dd6c34c23c4

Comment by Githook User [ 30/Apr/19 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'Kay Kim', 'username': 'kay-kim'}

Message: DOCS-9517,DOCSP-4513: rm recoverShardingState parameter
Branch: v3.6
https://github.com/mongodb/docs/commit/09febbdb1150ad701a073093bc4e13c0783eb1a9

Comment by Githook User [ 30/Apr/19 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-9517,DOCSP-4513: rm recoverShardingState parameter
Branch: v3.4
https://github.com/mongodb/docs/commit/8914575b7c7031b882d78bde5dfa9f1b51ac10b7

Comment by Githook User [ 12/Apr/19 ]

Author:

{'name': 'ravind', 'username': 'rkumar-mongo', 'email': 'ravind.kumar@10gen.com'}

Message: DOCS-9517: Update restore sharded cluster tutorial

DOCS-12315: Fixup for restore sharded cluster proc
Branch: v3.4
https://github.com/mongodb/docs/commit/fcf307ece064f69c54ab669835e6de98eb2fbc95

Comment by Ravind Kumar (Inactive) [ 08/Apr/19 ]

Note: fixups were done as part of DOCS-12315, required for backporting.

Comment by Ravind Kumar (Inactive) [ 07/Dec/18 ]

Deployed to master (4.2) through 3.6, need to apply one fixup to 3.4 guides and we're done here.

Comment by Githook User [ 07/Dec/18 ]

Author:

{'name': 'ravind', 'email': 'ravind.kumar@10gen.com', 'username': 'rkumar-mongo'}

Message: DOCS-9517: Update restore sharded cluster tutorial
Branch: v3.6
https://github.com/mongodb/docs/commit/1a26315aef32ffa57373492c18a7afa3d5063f4f

Comment by Githook User [ 07/Dec/18 ]

Author:

{'name': 'ravind', 'email': 'ravind.kumar@10gen.com', 'username': 'rkumar-mongo'}

Message: DOCS-9517: Update restore sharded cluster tutorial
Branch: v4.0
https://github.com/mongodb/docs/commit/b639fcf4bc51855c1224f022545661979f896b4e

Comment by Githook User [ 07/Dec/18 ]

Author:

{'name': 'ravind', 'email': 'ravind.kumar@10gen.com', 'username': 'rkumar-mongo'}

Message: DOCS-9517: Update restore sharded cluster tutorial
Branch: master
https://github.com/mongodb/docs/commit/e0f46cb96f4cd43a8a1bce252920d64b4993d0fe

Comment by Ravind Kumar (Inactive) [ 05/Nov/18 ]

Short update for interested parties: This ticket is still in progress. I'm testing to make sure that the refreshed procedure is working as expected.

Comment by Rakesh Kumar [ 15/Oct/18 ]

I am also getting below error while running step 6 command:

doc url : https://docs.mongodb.com/v3.4/tutorial/restore-sharded-cluster/

  1. MongoDB version v3.4.17
  2. # command out-put:
    BadValue: Illegal --setParameter parameter: "recoverShardingState"

  

> db.system.version.find()
> db.system.version.find(){ "_id" : "authSchema", "currentVersion" : 5 }
 
{ "_id" : "featureCompatibilityVersion", "version" : "3.4" }
{ "_id" : "shardIdentity", "clusterId" : ObjectId("5942ac975e5a1041fbedf601"), "shardName" : "rs02", "configsvrConnectionString" : "conf/mongo-int-B-conf-1.test.net:27019,mongo-int-B-conf-2.test.net:27019,mongo-int-B-conf-3.test.net:27019" }
{ "_id" : "minOpTimeRecovery", "configsvrConnectionString" : "conf/mongo-int-B-conf-1.test.net:27019,mongo-int-B-conf-2.test.net:27019,mongo-int-B-conf-3.test.net:27019", "shardName" : "rs02", "minOpTime" : { "ts" : Timestamp(1539250088, 11), "t" : NumberLong(14) }, "minOpTimeUpdaters" : 0 }
 
> db.system.version.remove({ _id: "minOpTimeRecovery" })
 
WriteResult({ "writeError" : { "code" : 13, "errmsg" : "not authorized on admin to execute command { delete: \"system.version\", deletes: [ { q: { _id: \"minOpTimeRecovery\" }, limit: 0.0 } ], ordered: true }" }})

 

 

Comment by Ravind Kumar (Inactive) [ 24/Jul/18 ]

Added notes based on some detective-ing to resolve this:

For 3.6+, Step 6 should be replaced with instructions on modifying the shardIdentity document to update the config server hostname configsvrConnectionString if it has changed. 

For 3.4, Modify Step 6 to focus on modifying minOpTimeRecovery document for updating the config server hostname configsvrConnectionString if it has changed

Comment by Asher Karadi [ 15/Dec/17 ]

Not missing, but rather incorrect and misleading... Step 6 mentions recoverShardingState which was removed.

Comment by Kaloian Manassiev [ 14/Dec/17 ]

The steps as listed on that link are correct. What you have described above isn't complete since it is missing step 5.

Comment by Asher Karadi [ 23/Jul/17 ]

Thank you for the prompt response Ravind.

It is not urgent, I was just testing restoration... However, as 3.4 is officially the current stable release, I think the documantation should be updataed asap to accomodate the recoverShardingState changes. When following this guide, it is not clear what should be done instead.

Thanks again,
Asher

Comment by Ravind Kumar (Inactive) [ 23/Jul/17 ]

Hi asher.karadi@zerto.com ,

The DOCS project tracks MongoDB documentation tickets. While we can try to provide you with some support, if your restoration job requires any urgency I recommend contacting MongoDB Professional Support.

In 3.4, you must start any mongod process that is to act as a shard with the --shardsvr option. This is regardless as to whether are performing a restoration procedure or simply restarting the shard server.

I believe that the ticket description you can see here is simply reiterating that the --shardsvr parameter must be present for a mongod to act as a shard in a sharded cluster. I can confirm this with the engineer who owned the original changes and get back to you, but again if this is urgent please consider opening a support ticket.

Comment by Asher Karadi [ 23/Jul/17 ]

Hello,

What is the correct way to start without recovery using 3.4.4?
I'm trying to restore my cluster and I'm not sure if starting mongod without --shardsvr will suffice.

Thanks,
Asher

Comment by Kelsey Schubert [ 09/Mar/17 ]

Please note that https://docs.mongodb.com/manual/tutorial/restore-sharded-cluster/#clear-per-shard-sharding-recovery-information will have to be updated as result of this change.

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