Top entries may remain if write conflict occurs during dropDatabase

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.4.0-rc2
    • Affects Version/s: 3.3.15
    • Component/s: Diagnostics
    • None
    • Fully Compatible
    • ALL
    • Hide

      Apply the attached repro.patch, then run

      $ python buildscripts/resmoke.py --executor no_passthrough_with_mongod jstests/noPassthroughWithMongod/top_drop.js
      Show
      Apply the attached repro.patch , then run $ python buildscripts/resmoke.py --executor no_passthrough_with_mongod jstests/noPassthroughWithMongod/top_drop.js
    • Integration 2016-10-10, Integration 2016-10-31
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a database is dropped, dropDatabase() removes each collection from Top. If a write conflict exception occurs before or during this loop, entries may remain in Top even after dropDatabase() finishes successfully.

        1. repro.patch
          1 kB

              Assignee:
              Kyle Suarez (Inactive)
              Reporter:
              Kyle Suarez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: