[DOCS-8793] Document changes to removeShard procedure for 3.2 branch only Created: 08/Sep/16  Updated: 30/Oct/23

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

Type: Task Priority: Minor - P4
Reporter: Andy Schwerin Assignee: Kay Kim (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-25516 Add setParameter option to 3.2 to pre... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

With SERVER-25516, we should document a change to the "remove shard" procedure for versions 3.2.10 through the end of the 3.2 line (but not 3.4 and beyond).

Specifically, when removing a shard, if any mongos or mongod nodes start producing annoying log messages about hosts from the removed shard being unreachable, or if the operator wishes to re-add the shard using different hosts at a later date, the operator has two choices:

  1. Restart all the nodes with the annoying log messages
  2. Toggle the timeOutMonitoringReplicaSets server parameter introduced in SERVER-25516 from "false" to "true" on each offending node for 2 minutes, and then toggle it back.

This behavior will only be available in 3.2.10+, and will be unnecessary in the 3.4 and subsequent releases.



 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 07:56:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.