[DOCS-11809] Docs for SERVER-33237: Optimize the Range Deleter speed Created: 17/Jun/18  Updated: 13/Nov/23  Resolved: 05/Dec/18

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 3.6.7, 3.4.17, 4.0.1, 4.1.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-33237 Optimize the Range Deleter speed Closed
Related
is related to DOCS-12241 Docs for SERVER-37080: Implement tune... Closed
Participants:
Days since reply: 5 years, 10 weeks ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description:

Document the new rangeDeleterBatchDelayMS server parameter.

Scope of changes:

Impact to other docs outside of this product:

MVP:

Resources:

Engineering Ticket Description:

The sharding range deleter was intentionally implemented to not be fully efficient in order to minimize its interference with MMAP V1. This causes orphaned data to accumulate especially with the recent moveChunk improvements.

With the WiredTiger storage engine, we can let it run at full speed and we should investigate the benefit of directly instantiating an auto-yielding delete stage instead of recreating the index scan phase for each document.



 Comments   
Comment by Githook User [ 05/Dec/18 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@mongodb.com'}

Message: DOCS-11809: rangeDeleterBatchDelayMS parameter
Branch: v3.4
https://github.com/mongodb/docs/commit/74c96af369fe98da7e3e5ccd924659863705b16f

Comment by Githook User [ 05/Dec/18 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@mongodb.com'}

Message: DOCS-11809: rangeDeleterBatchDelayMS parameter
Branch: v3.6
https://github.com/mongodb/docs/commit/f1a304784f71f8eca04080f7f2b0d3f0c1207bc3

Comment by Githook User [ 05/Dec/18 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@mongodb.com'}

Message: DOCS-11809: rangeDeleterBatchDelayMS parameter
Branch: v4.0
https://github.com/mongodb/docs/commit/5fac0c0fec4ed61123c3fe8da39df5966b39fda6

Comment by Githook User [ 05/Dec/18 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@mongodb.com'}

Message: DOCS-11809: rangeDeleterBatchDelayMS parameter
Branch: master
https://github.com/mongodb/docs/commit/f7dffbaaee4c762ba002433ec811391b59e6ed9d

Comment by Kay Kim (Inactive) [ 28/Nov/18 ]

So, we generate the corresponding docs ticket when the server ticket is resolved/closed and the server ticket is marked as docs changes needed.

Comment by Kevin Pulo [ 21/Nov/18 ]

Would be good to also document rangeDeleterBatchSize (SERVER-37616), as well as (maybe) migrateCloneInsertionBatchSize and migrateCloneInsertionBatchDelayMS (SERVER-37080).

Comment by Kevin Pulo [ 29/Aug/18 ]

In addition to directly documenting the rangeDeleterBatchDelayMS parameter, it would also be good to get an entry added to the 3.4 ChangeLog regarding the behaviour in that branch (as explained in this comment).

Generated at Thu Feb 08 08:03:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.