Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-4429

When moving primary need to inform all other mongoses

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • ALL

      The new shard for a database on movePrimary is not propagated to mongos automatically - this should trigger a StaleConfigException on a sharded connection.

        1. mongos_move_primary_weirdness.js
          0.9 kB

            Assignee:
            Unassigned Unassigned
            Reporter:
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: