Error
Error Code:
300
MongoDB Error 300: Collection UUID Missing During Deletion
Description
This error indicates that a range deletion operation was initiated but could not be completed because the target collection, identified by its UUID, does not exist in the database. This typically occurs when a collection is dropped or renamed while a deletion operation is in progress or pending.
Error Message
Range Deletion Abandoned Because Collection With U U I D Does Not Exist
Known Causes
3 known causesCollection Dropped or Renamed
The collection targeted by the range deletion was dropped or renamed between the time the operation was planned and its execution.
Stale Metadata Reference
MongoDB's internal metadata or a client's cached information holds a reference to a collection UUID that no longer corresponds to an active collection.
Replication Lag/Inconsistency
In a replica set, a secondary member might attempt a range deletion based on an oplog entry, but the target collection might not exist on that specific secondary due to replication lag or a prior inconsistency.
Solutions
Coming SoonDetailed step-by-step solutions for this error are being prepared. In the meantime, try these general troubleshooting tips:
General Troubleshooting Tips
- Check the error message carefully for specific details
- Review recent changes that might have caused the error
- Search for the exact error code in the official documentation
- Check log files for additional context
- Try restarting the application or service