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

Tighten conditions when it's safe to use movePrimary

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • v1.3.4
    • None
    • manual
    • None

    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

            sam.kleinman Sam Kleinman (Inactive)
            thomas.rueckstiess@mongodb.com Thomas Rueckstiess
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              9 years, 33 weeks ago