[DOCS-12224] for running standalone, "recoverShardingState: false" is required if SCCC were formerly used Created: 28/Nov/18  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 3.2.19
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Kay Agahd Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

linux debian 64


Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

At least for version 3.2.19 (which were upgraded from a former mongodb cluster still using SCCC to a cluster using in 3.2.19 CSRS) you missed out the following parameter:

recoverShardingState: false

Both pages are missing it:
https://docs.mongodb.com/manual/tutorial/perform-maintence-on-replica-set-members/
https://docs.mongodb.com/v3.2/tutorial/build-indexes-on-replica-sets/

 

 

 

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Comment by Kay Agahd [ 18/Jan/19 ]

Why is an update of the documentation so slow? The time you need to update the documentation will made it obsolete since nobody will use v3.2 anymore. Is that your intention?

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