Large number of collections causes extreme dropDatabase slowness

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Critical - P2
    • None
    • Affects Version/s: 3.2.3
    • Component/s: WiredTiger
    • None
    • Environment:
      Ubuntu 12.04 Linux
      EC2 - i2.4xlarge
      Kernel 3.13.0-79-generic

      Set of 3 in a replicaset
    • Linux
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Create a database with few thousand collections, try and drop the database. For a database of only a few hundred megabytes, took over a half hour to delete. "show dbs" was hung during that time as well. If I just create a database with one collection and one document, I can delete things just fine.

      I'm currently graphing all metrics from serverStatus so let me know if theres any values you think are relevant to help debugging the issue. I'll add more information to this issue as I find it since I'm still running tests but wanted to get the discussions going.

        1. diagnostic.tar.gz
          30.65 MB
        2. mongo_collection_creation.js
          0.4 kB
        3. mongo.conf
          0.3 kB
        4. mongo.log
          1 kB

            Assignee:
            Kelsey Schubert
            Reporter:
            Justin Lintz
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: