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

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

    XMLWordPrintableJSON

Details

    • ServerDocs2020: Aug24 - Aug31, ServerDocs2020: Aug31 - Sep07

    Description

      Description

      Similar to DOCS-8514 dropping a collection and then reusing the name to create another collection in a sharded environment can lead to stale cache SERVER-17397

      https://docs.mongodb.com/manual/reference/method/db.collection.drop/ should warn that dropping and reusing a collection name requires complex cache flushing 

      Alternatively the docs could add that to avoid this problem, use remove({}) instead and manually drop any unneeded collections. 

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. DOCS-15797 Remove deprecated note for collection.drop()

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

          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-8514 dropDatabase in sharded environments should point out that all mongos instances need cache refreshed

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

          Activity

            People

              jason.price@mongodb.com Jason Price
              nicholas.cottrell@mongodb.com Nic Cottrell
              Jess Mokrzecki Jess Mokrzecki
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                3 years, 3 weeks, 2 days ago