Infinite log messages after dropping database

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 8.0.11
    • Component/s: None
    • None
    • ALL
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We are experiencing the same probleme described in SERVER-90057.

      We start the mongod with this configuration :

      net:
    bindIp: 127.0.0.1
    port: 27017
operationProfiling:
    mode: 'off'
processManagement:
    timeZoneInfo: /usr/share/zoneinfo
setParameter:
    diagnosticDataCollectionEnabled: true
storage:
    dbPath: /var/lib/mongo
    directoryPerDB: true
systemLog:
    destination: file
    logAppend: true
    logRotate: reopen
    path: /var/log/mongodb/mongo.log
    quiet: true

      We also tried without directoryPerDB : the bug occurs the same way.

      We execute mongosh to drop the database :

      mongosh --quiet --eval "db.getMongo().getDBNames().filter(name => name.match(\"^$database_name$\")).forEach(function(i){db.getSiblingDB(i).dropDatabase()})"

      In the case of the log sent, the variable database_name is 'quartz-training'.

      This is executed in our CI, several times a day.
      The bug occurs sometimes, on some index that seems impossible to delete (not always the sames).

      Please find enclosed the log file : mongo.log.dropissue .

      The only way to exit this situation is to restart mongod : if I attempt a drop of database, it's successful.

        1. mongo.log.dropissue
          1.96 MB

            Assignee:
            Unassigned
            Reporter:
            Anne Luagn
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: