[DOCS-9521] Docs for SERVER-22663: Make --shardsvr required for a mongod to be used as a shard Created: 05/Dec/16  Updated: 24/Jan/18  Resolved: 24/Jan/18

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

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

Issue Links:
Documented
documents SERVER-22663 Make --shardsvr required for a mongod... Closed
Participants:
Days since reply: 7 years, 10 weeks, 2 days ago

 Description   

Engineering Ticket Description:

3.4 onwards:

a shard can become shard aware in two ways:

  • started with --shardsvr and shardIdentity document found on disk
  • started with --shardsvr and receive shardIdentity insert

so, we will eventually reject all sharding commands if:

  • not started with --shardsvr
  • started with --shardsvr but not yet sharding aware

=============

for backwards compatibility with 3.2:

a shard can also become shard aware if:

  • started with --shardsvr and receive command that initializes sharding awareness

so (what this ticket does):

reject all sharding commands except a whitelist of commands that initialize sharding awareness.


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