0

On a fresh Mongo DB 8.0 mono instance (no cluster) community edition install on Debian and through the package manager, i have a recurring error message in my logs saying this:

"c":"STORAGE",  "id":22237,   "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"collection-538-11424269811010067358","dropTimestamp":{"$timestamp":{"t":0,"i":0}}}}
"c":"STORAGE",  "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"collection-538-11424269811010067358","dropTimestamp":{"$timestamp":{"t":0,"i":0}},"error":{"code":314,"codeName":"ObjectIsBusy","errmsg":"Failed to remove drop-pending ident collection-538-11424269811010067358"}}
"c":"STORAGE",  "id":22237,   "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"index-593-1142426981101006735
"c":"STORAGE",  "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"index-593-1142426981
"c":"STORAGE",  "id":22237,   "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"index-774-1142426981101006735
"c":"STORAGE",  "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"index-774-1142426981
"c":"STORAGE",  "id":22237,   "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"index-829-1142426981101006735
"c":"STORAGE",  "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"index-829-1142426981
"c":"STORAGE",  "id":22237,   "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"collection-773-11424269811010
"c":"STORAGE",  "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"collection-773-11424
"c":"STORAGE",  "id":22237,   "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"index-780-1142426981101006735
"c":"STORAGE",  "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"index-780-1142426981
"c":"STORAGE",  "id":22237,   "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"collection-779-11424269811010
"c":"STORAGE",  "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"collection-779-11424
"c":"STORAGE",  "id":22237,   "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"index-782-1142426981101006735
"c":"STORAGE",  "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"index-782-1142426981
"c":"STORAGE",  "id":22237,   "ctx":"TimestampMonitor","msg":"Completing drop for ident","attr":{"ident":"index-832-1142426981101006735
"c":"STORAGE",  "id":6936300, "ctx":"TimestampMonitor","msg":"Drop-pending ident is still in use","attr":{"ident":"index-832-1142426981

Combined with recurring:

"dropTimestamp":{"$timestamp":{"t":0,"i":0}},"error":{"code":314,"codeName":"ObjectIsBusy","errmsg":"Failed to remove drop-pending ident index-13706-11424269811010067358"}}}

I restarted the MongoDB service, still have available space on the disk, it looks like my permissions are OK but i don't understand how to fix this issue or how to identify a way to solve it. The documentation doesn't say much how to solve this issue.

Does anyone have a suggestion? Thanks.

Improve this question

2 Answers 2

Reset to default
0

When the user/application drops a collection, the mongod first renames it and all of its indexes to a temporary drop-pending name. After all members of the replica set have propagated that change, they drop those pending items.

If mongod is restarted, it scans for any drop-pending items and resumes that process.

The error messages you show indicate that it is trying to drop them, but is finding that there is a cursor of some sort still open on them, so it will try again later.

Note from the severity on the log message that these are informational.

Improve this answer
5
  • The problem is that those logs are repeating but the server is still in dev phase so no action is really happening flushing the collections :/. Commented Oct 30 at 13:02
  • Do the messages come back after restarting the node? Commented Nov 6 at 9:52
  • Yes it keeps happening after restarting the node. Commented Nov 7 at 9:36
  • In the messages shown, no single ident is seen twice. Are the idents noted in the messages always different? Commented Nov 9 at 3:19
  • Yes, there are repetitions. The same ~400 lines of the expect quoted are repeating every second. The daily log has 32 million lines (matching 400 * 86400). Commented Nov 10 at 9:31
0

Please note that, In MongoDB, when you drop a collection or index, it may not be deleted immediately. Instead, it enters a "drop-pending" state, especially in replica sets, until it is safe to remove—after replication and commit across nodes. The "ObjectIsBusy" error means MongoDB cannot proceed because the object, such as an index, is still active or not fully deleted.

This status is internal and usually clears automatically once MongoDB finishes its background cleanup.

As you said it is fresh mongo that curious me if there was already older version of mongod ran and abandoned? If it is fresh you can clear the dbpath and try start them

Thanks, Darshan

Improve this answer
1
  • The server is new so no older version exists. What do you mean by "clear the dbpath"? Commented Oct 30 at 13:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.