[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: |
|
||||||||||||
| 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.
|