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

dropDatabase in sharded environments should point out that all mongos instances need cache refreshed

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • None
    • None
    • None
    • true

    Description

      Hey team,

      after running a dropDatabase and then creating a new database with the same name will leave mongos instances, other than the one that dropped the database, with old information about where the "primary shard" for the database is. Please see SERVER-15213.

      We have a warning on movePrimary about mongos concurrency issue and we feel that the same warning should be on dropDatabase.

      Regards,
      Roy Rim

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17397 Dropping a Database or Collection in a Sharded Cluster may not fully succeed

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. DOCS-13703 drop collection in sharded environments should point out that all mongos instances need cache refreshed

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              kay.kim@mongodb.com Kay Kim (Inactive)
              roy.rim@mongodb.com Roy Rim
              Jess Mokrzecki Jess Mokrzecki
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                4 years, 32 weeks, 5 days ago