As of SERVER-74033, we drop WT tables without "force=true", but as a result, we print errors every second until a checkpoint takes place, by default every minute
2023-03-09T09:03:20.091+00:00 I STORAGE [TimestampMonitor] Completing drop for ident {"ident":"collection-2--2259663256765783329","dropTimestamp":{"$timestamp":{"t":0,"i":0}}}
2023-03-09T09:03:17.091+00:00 I STORAGE [TimestampMonitor] Drop-pending ident is still in use {"ident":"collection-2--2259663256765783329","dropTimestamp":{"$timestamp":{"t":0,"i":0}},"error":{"code":314[30/1834]
e":"ObjectIsBusy","errmsg":"Failed to remove drop-pending ident collection-2--2259663256765783329"}}
We should clean this up, because it's quite noisy and looks like there is a problem when there is not.
- is caused by
-
SERVER-74033 Remove ident force drop in favour of handling ENOENT
-
- Closed
-