Info

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.

Top User Comments

louis.williams commented on Wed, 5 Jun 2024 14:45:23 +0000: We found one bug in SERVER-91013, and I don't remember where I saw these logs. Closing for now louis.williams commented on Thu, 2 May 2024 19:26:44 +0000: We're going to revisit this in a few sprints to see if we need to do it once fixing the underlying problem

Steps to Reproduce