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

Better story for mongos refresh when another mongos dropped a database

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 2.4.0-rc2
    • Sharding
    • None
    • ALL

    Description

      Setup: 2 mongos, 1 shard

      1. Enable sharding on test db ysing mongos A.
      2. Use mongos B to perform a query against test db.
      3. Use mongos A to drop test db.
      4. Trying to enable sharding with mongos B gives the result:

      { "ok" : 0, "errmsg" : "already enabled" }

      Current workaround is to force mongos B to refresh it's config with

      { flushRouterConfig: 1 }

      Also attaching script demonstrating the behavior (stale_db.js).

      Attachments

        Activity

          People

            Unassigned Unassigned
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: