Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-14651

listDatabases command errors under high database create/delete load

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.2.7, 2.4.10, 2.6.3
    • Component/s: Storage
    • Labels:
      None
    • ALL
    • Hide

      [PERL-387] has example code that replicates the problem.

      In short: have several threads/processes repeatedly and rapidly create a database, add a document to a collection, and then drop the database. In another thread/process, call "listDatabases" once a second until the error occurs.

      Show
      [PERL-387] has example code that replicates the problem. In short: have several threads/processes repeatedly and rapidly create a database, add a document to a collection, and then drop the database. In another thread/process, call "listDatabases" once a second until the error occurs.

      If many databases are rapidly created and deleted, the listDatabases command can fail with error 15927 ("can't open database in a read lock..."), which apparently is from database_holder.cpp.

      I think listDatabases needs to catch that error and either retry or just omit the offending database in the list it returns. Otherwise, a transient error from a single database prevents the rest of the valid results from being returned.

            Assignee:
            Unassigned Unassigned
            Reporter:
            david.golden@mongodb.com David Golden
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: