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

ObjectIsBusy errors from deferred ident drops are too noisy

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • Execution Team 2024-06-10

      For various reasons, we can fail to drop deferred WT tables, which creates excessively noisy logs like this:

      [j9:c:prim] | 2024-04-23T07:18:39.593+00:00 I  STORAGE  22237   [S] [TimestampMonitor] "Completing drop for ident","attr":{"ident":"internal-525-12582837108598312458","dropTimestamp":{"$timestamp":{"t":0,"i":0}}}
      
      [j9:c:prim] | 2024-04-23T07:18:39.593+00:00 I  STORAGE  6936300 [S] [TimestampMonitor] "Drop-pending ident is still in use","attr":{"ident":"internal-525-12582837108598312458","dropTimestamp":{"$timestamp":{"t":0,"i":0}},"error":{"code":314,"codeName":"ObjectIsBusy","errmsg":"Failed to remove drop-pending ident internal-525-12582837108598312458"}}
      

      These logs are not very useful at the default log level and generate a lot of noise in our testing because they often wait for a checkpoint to finish.

            Assignee:
            louis.williams@mongodb.com Louis Williams
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: