[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: |
|
||||||||||||||||||||||||
| 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: | ||||||||||
| Comment by Githook User [ 30/Apr/19 ] | ||||||||||
|
Author: {'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}Message: | ||||||||||
| Comment by Githook User [ 30/Apr/19 ] | ||||||||||
|
Author: {'email': 'kay.kim@10gen.com', 'name': 'Kay Kim', 'username': 'kay-kim'}Message: | ||||||||||
| Comment by Githook User [ 30/Apr/19 ] | ||||||||||
|
Author: {'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}Message: | ||||||||||
| Comment by Githook User [ 12/Apr/19 ] | ||||||||||
|
Author: {'name': 'ravind', 'username': 'rkumar-mongo', 'email': 'ravind.kumar@10gen.com'}Message:
| ||||||||||
| Comment by Ravind Kumar (Inactive) [ 08/Apr/19 ] | ||||||||||
|
Note: fixups were done as part of | ||||||||||
| 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: | ||||||||||
| Comment by Githook User [ 07/Dec/18 ] | ||||||||||
|
Author: {'name': 'ravind', 'email': 'ravind.kumar@10gen.com', 'username': 'rkumar-mongo'}Message: | ||||||||||
| Comment by Githook User [ 07/Dec/18 ] | ||||||||||
|
Author: {'name': 'ravind', 'email': 'ravind.kumar@10gen.com', 'username': 'rkumar-mongo'}Message: | ||||||||||
| 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/
| ||||||||||
| 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, | ||||||||||
| Comment by Ravind Kumar (Inactive) [ 23/Jul/17 ] | ||||||||||
|
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? Thanks, | ||||||||||
| 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. |