Hi @Mait_S There is no direct way to increase the time limit for orphaned range deletion during migration. There are multiple reasons behind this. This problem can be caused by a large number of orphaned documents that need to be deleted, which may result in timeouts, especially on busy or resource-constrained servers. Slow disk performance or I/O bottlenecks can also contribute, as deleting many documents or scanning large collections takes significant time. Additionally, high server load, heavy write operations, or other ongoing migrations can slow down the orphan cleanup process. Finally, if certain shards are overloaded or have an imbalance of data, range deletions during migrations can become even slower and more prone to timing out.
As Wernfried mentioned above, this is informational error and won’t have any severe impact. MongoDB will often retry and eventually clear up orphans on the next migration or cleanup pass. if it occurring very frequent, you can focus on operational optimizations (I/O, indexing, balancing) and monitor the balancer and migration logs for persistent issues if any.
Hope this helps!
