Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-8793

Document changes to removeShard procedure for 3.2 branch only

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Minor - P4
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: manual, Server
    • Labels:
      None

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              schwerin Andy Schwerin
              Participants:
              Last commenter:
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Days since reply:
                4 years, 35 weeks, 6 days ago