[DOCS-16172] [SERVER] Clarify on which process(es) it makes sense to set sharding server parameter Created: 31/May/23  Updated: 22/Jan/24

Status: Backlog
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: backlog, proactive, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 36 weeks ago

 Description   

The sharding parameters documentation page is listing all sharding server parameters. Most of such parameters only take effect when set on some specific process (routers, shards, config server) while setting them on other processes makes no sense.

That section must be enhanced to clarify for each parameter on which kind of process(es) it makes sense to set them:

  • mongos (router)
    AND/OR
  • mongod (shards)
    AND/OR
  • mongod (config server)

For some parameters it's clearly specified on which nodes they must be set while others are under-documented in this regard.

Examples:

  • For balancerMigrationsThrottlingMs it's clearly stated that "This parameter only takes effect on config server nodes."
  • For chunkDefragmentationThrottlingMS there is no such indication, even though also this parameter only takes effect on config server nodes

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