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

Tighten conditions when it's safe to use movePrimary

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • v1.3.4
    • Affects Version/s: None
    • Component/s: manual
    • None

      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

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

              Created:
              Updated:
              Resolved:
              10 years, 14 weeks, 1 day ago