MongoDB Log-Overflow Crash

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Critical - P2
    • None
    • Affects Version/s: 8.0.9
    • Component/s: Replication, Storage
    • None
    • ALL
    • Hide

      Unknown, 10 days ago it began happening and I noticed no disruption until it filled the disk space entirely. Feels like an odd one-off case that can be mitigated by only attempting the operation a fixed number of times or for a fixed time length before timing out.

       

      Has been mentioned in previous issues on the internet:

      https://www.findbugzero.com/operational-defect-database/vendors/mongodb/defects/2284645

      https://www.findbugzero.com/operational-defect-database/vendors/mongodb/defects/2659446

       

      Show
      Unknown, 10 days ago it began happening and I noticed no disruption until it filled the disk space entirely. Feels like an odd one-off case that can be mitigated by only attempting the operation a fixed number of times or for a fixed time length before timing out.   Has been mentioned in previous issues on the internet: https://www.findbugzero.com/operational-defect-database/vendors/mongodb/defects/2284645 https://www.findbugzero.com/operational-defect-database/vendors/mongodb/defects/2659446  
    • None
    • 0
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

       

      {"t":{"$date":"2025-06-11T05:05:48.994+00:00"},"s":"I",  "c":"STORAGE",  "id":22260,   "ctx":"TimestampMonitor","msg":"Removing drop-pending idents with drop timestamps before timestamp","attr":{"timestamp":{"$timestamp":{"t":0,"i":0}}}}
{"t":{"$date":"2025-06-11T05:05:48.994+00:00"},"s":"I",  "c":"STORAGE",  "id":22237,   "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"index-28-16423051353446739403","dropTimestamp":{"$timestamp":{"t":0,"i":0}}}}
{"t":{"$date":"2025-06-11T05:05:48.994+00:00"},"s":"I",  "c":"STORAGE",  "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"index-28-16423051353446739403","dropTimestamp":{"$timestamp":{"t":0,"i":0}},"error":{"code":314,"codeName":"ObjectIsBusy","errmsg":"Failed to remove drop-pending ident index-28-16423051353446739403"}}}

       

      Over the course of approximately 10 days, mongod.log file has grown to 67 GiB in size and eventually crashed the server by filling all available storage space. The error above has been repeated in the log file every single second for those past 10 days. 

       

      The database has been completely operation up until the point where the system ran out of drive space and there are no other operational defects. I am running Ubuntu 24.04.2 LTS on an ARM system. There is no other application that I am aware of accessing the /data/db folder. A possible fix is timing out the operation after a certain amount of tries instead of repeatedly attempting for infinitely.

       

            Assignee:
            Unassigned
            Reporter:
            Cowings N/A
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: