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

Tighten conditions when it's safe to use movePrimary

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: v1.3.4
    • Component/s: manual
    • Labels:
      None
    • Last comment by Customer:
      true
    • Actual Time:
      4

      Description

      The conditions when it is safe to call movePrimary need to be tighter than currently documented, and we should mention that the other mongos do not know about the change until restarted/flushRouterConfig'ed.

      I wrote a draft, here the pull request:
      https://github.com/mongodb/docs/pull/1736

        Attachments

          Activity

            People

            Assignee:
            sam.kleinman Sam Kleinman (Inactive)
            Reporter:
            thomasr Thomas Rueckstiess
            Participants:
            Last commenter:
            Jonathan Dahl Jonathan Dahl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since reply:
              7 years, 25 weeks, 3 days ago
              Date of 1st Reply: