Error
Error Code:
265
MongoDB Error 265: Orphaned Range Cleanup Failure
Description
Error 265, 'Orphaned Range Clean Up Failed', indicates that MongoDB's background process for removing orphaned data from sharded collections could not complete successfully. This typically occurs in sharded clusters after chunk migrations, where residual data from moved chunks remains on the source shard, leading to inconsistencies if not cleaned up.
Error Message
Orphaned Range Clean Up Failed
Known Causes
4 known causesShard Inconsistencies
Data inconsistencies, corrupted indexes, or operational issues on one or more shards can prevent the cleanup process from correctly identifying or removing orphaned documents.
Network Connectivity Problems
Intermittent or persistent network issues between config servers, mongos instances, and shards can disrupt the communication necessary for the cleanup operation to succeed.
Resource Limitations
Excessive load, insufficient CPU, memory, or disk I/O on sharded cluster members can prevent the orphaned range cleanup operation from completing within its allocated time or resources.
Concurrent Operations or Locks
Heavy writes, ongoing data migrations, or other administrative operations occurring concurrently can create locks or contention that prevent the cleanup process from progressing.
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