[DOCS-11210] Suggest that users should be avoiding frequent restarts of mongoS Created: 15/Jan/18  Updated: 30/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

At present chunk splits are initiated by a mongoS when the amount of data written into the chunk (tracked by the mongoS) exceeds the threshold of 20% of the maximum chunk size.

When mongoS is restarted, that re-sets the data written counter, which in return can delay splits causing chunks to grow beyond the splitting threshold and even beyond the maximum chunk size threshold. Eventually such chunks can be split in a cascading fashion, adding (potentially significant) balancing overhead.

The documentation should suggest that:

  • frequent restarts of mongoS should be avoided, when possible
  • the flushRouterConfig command should only be executed in exceptional circumstances, when there is a good reason to do so. It should not be run for prevention purposes on regular basis


 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!

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