[DOCS-11323] Docs for SERVER-32569: Introduce uniform way to allow config servers and shard replica sets to start in non-cluster mode Created: 14/Feb/18  Updated: 29/Oct/23  Resolved: 26/Jun/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 3.2.19, 3.4.11, 3.7.2, 3.6.3

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-32569 Introduce uniform way to allow config... Closed
Participants:
Days since reply: 5 years, 33 weeks, 1 day ago
Epic Link: DOCS: 4.0 Server

 Description   

Documentation Request Summary:

The new startup parameter should be documented.

Description

Added new startup parameter

--setParameter skipShardingConfigurationChecks=true

Only for use when starting a shard or config server as a standalone for maintenance ops.

Scope of changes (files that need work and how much)

  • parameter
  • Add ref to shardsvr and configsvr 

Note: Some confusion between this and HELP-6145, which implies this flag might only be required for 3.2. Need to test this for each MongoDB version and see what happens.

Impact to other docs outside of this product

N/A

MVP (work and date?)

  • Update 3.2 docs (0.25)
  • Update 3.4 docs (0.1)
  • Update 3.6 docs (0.1)

Since this would break the aforementioned tutorials, suggest setting as P2 and resolving by first week of April.

Resources (e.g. Scope Docs, Invision)

N/A

Engineering Ticket Description:

Starting with MongoDB version 3.2, all sharding database components (config server and shard replica sets) persist the fact that they belong to a sharded cluster. This information is stored in two places - the cluster identity document and the replica set configuration (config servers only).

Once this information persisted, it is not possible to restart a config server or shard as an independent replica set, because startup will fail if -configsvr or -shardsvr are missing. This serves as a protection against customers inadvertently omitting startup parameters and misconfiguring their systems, but it also prevents the shard to be started up for maintenance (e.g., restore).

In order to unify the non-cluster behaviour across all versions and unblock the Cloud team, on all versions starting from 3.2 we will introduce a new startup-only parameter on mongod called --setParameter skipShardingConfigurationChecks=true, which is incompatible with --configsvr or --shardsvr. The meaning of this flag is "I am planning to restore directly into the node, I know what I am doing and I don't want any sharding validations or background threads to run".

This flag will make this and this checks conditional on the flag being enabled, so that replica set nodes will not fail to start or start as REMOVED.



 Comments   
Comment by Githook User [ 26/Jun/18 ]

Author:

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

Message: DOCS-11323: add versionchanged
Branch: v3.6
https://github.com/mongodb/docs/commit/4723572fbc617730fa62a20a6ee124cfc6548b88

Comment by Githook User [ 26/Jun/18 ]

Author:

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

Message: DOCS-11323: update the change oplog tutorial
Branch: v3.2
https://github.com/mongodb/docs/commit/b552580956c22e72e4385a38871cbcd52bd4dc3c

Comment by Githook User [ 26/Jun/18 ]

Author:

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

Message: DOCS-11323: update the change oplog tutorial
Branch: v3.4
https://github.com/mongodb/docs/commit/eb627c8e8935658234dd7254a116ebbfce79e691

Comment by Githook User [ 26/Jun/18 ]

Author:

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

Message: DOCS-11323: tweak wording
Branch: v3.6
https://github.com/mongodb/docs/commit/6c35308baf5b9d6e29b90a6addd2be2273da45e0

Comment by Githook User [ 26/Jun/18 ]

Author:

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

Message: DOCS-11323: tweak wording
Branch: master
https://github.com/mongodb/docs/commit/4361ba69846f4846f3e3bf09b6978abdbcc1398b

Comment by Githook User [ 26/Jun/18 ]

Author:

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

Message: DOCS-11323: skipShardingConfigurationChecks
Branch: v3.2
https://github.com/mongodb/docs/commit/8121f837c4396e4f3c2e6c7fbb7f664507157ddc

Comment by Githook User [ 26/Jun/18 ]

Author:

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

Message: DOCS-11323: skipShardingConfigurationChecks
Branch: v3.4
https://github.com/mongodb/docs/commit/d3c49aaee40fcd4b4dd5b198fa3da2c2fe8bd6cc

Comment by Githook User [ 26/Jun/18 ]

Author:

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

Message: DOCS-11323: tweak versions for backport
Branch: v3.6
https://github.com/mongodb/docs/commit/87bc6a7bef147d94155a2948092531579147cfbd

Comment by Githook User [ 26/Jun/18 ]

Author:

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

Message: DOCS-11323: skipShardingConfigurationChecks
Branch: v3.6
https://github.com/mongodb/docs/commit/64beac22c240ca1f56181a316ebb92284feb3708

Comment by Githook User [ 26/Jun/18 ]

Author:

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

Message: DOCS-11323: skipShardingConfigurationChecks
Branch: master
https://github.com/mongodb/docs/commit/db54c715baea93518369082292e4efae15d0b3ea

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