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

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      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

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

              Created:
              Updated:
              Resolved:
              5 years, 37 weeks, 1 day ago