[DOCS-3692] Best practices for deletes Created: 01/Jul/14  Updated: 11/Jan/17  Resolved: 15/Oct/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Task Priority: Major - P3
Reporter: Charlie Page Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates DOCS-1524 Broad guidance for typical performanc... Closed
Related
Participants:
Days since reply: 9 years, 33 weeks, 1 day ago

 Description   

Deletes incur high write lock. This will likely change in 2.6 in some ways. But dropping a collection/database will still be extremely fast. This ticket is to create a docs page to cover this.

  • Drop collections/database
  • TTL (if time period is known) to spread out deletes (docs all expiring at the same time isn't good)
  • Throttle deletes
    • pause between batches
    • w:majority to throttle

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