[SERVER-26316] cleanupOrphaned command is too slow Created: 26/Sep/16  Updated: 26/Sep/16  Resolved: 26/Sep/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: abhishek mishra Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-6210 Clean up data left behind on shards b... Closed
Related
related to SERVER-3645 Sharded collection counts (on primary... Closed
Operating System: ALL
Participants:

 Description   

I have created Sharded cluster with 3 shards. while balancer was moving the chunk, i executed count query on sharded collection & found that it is giving mismatched count.

I came to know about cleanupOrphaned command which removes invalid documents from the shard & executed on the primary node. It has taken more than 4 days time (i.e. 96 hours) to remove 1.8M records.

First of all why we need to run this command manually, it should have been automatically handled during balancing process. Even after running this command, It takes too much time to remove document. Is there any faster method to clear orphaned file?

Thanks.....



 Comments   
Comment by Kelsey Schubert [ 26/Sep/16 ]

Hi abhishek.mishra@cheersin.com,

Thanks for opening this ticket. I've linked to a couple related tickets that I would recommend reviewing, voting, and watching for updates. SERVER-3645 would address the issue that count commands can return too many results, and SERVER-6210 would automate some or all of the cleanup process either as a periodic background job or by being called on the receiver shard when migration fails. I believe SERVER-6210 fulfills your request that this be automatically handled.

I would recommend posting on the mongodb-users group, which provides MongoDB-related support. This would be the best place for your question regarding the performance of cleanupOrphaned. If you post to the user group, please include additional information about your environment to help others identify possible issues. For example, which version of MongoDB are you using? which storage engine? and what are your machine's specs?

Thank you,
Thomas

Generated at Thu Feb 08 04:11:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.