[DOCS-10046] cleanupOrphaned performance clarification Created: 28/Mar/17  Updated: 30/Oct/23  Resolved: 17/May/21

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Stennie Steneker (Inactive) Assignee: Stennie Steneker (Inactive)
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 2 years, 38 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

The cleanupOrphaned Performance section has wording that implies a document (or collection) scan:

cleanupOrphaned scans the documents in the shard to determine whether the documents belong to the shard. As such, running cleanupOrphaned can impact performance; however, performance will depend on the number of orphaned documents in the range.

However, cleanupOrphaned only makes sense with the context of the shard key so presumably uses the shard key index. The startingFromKey parameter defaults to minKey and is only valid if it matches the shard key pattern:

https://github.com/mongodb/mongo/blob/master/src/mongo/db/s/cleanup_orphaned_cmd.cpp#L97



 Comments   
Comment by Jeffrey Allen [ 17/May/21 ]

Closing as "Gone Away" but happy to reopen if there are adjustments to make.

Generated at Thu Feb 08 07:59:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.