[DOCS-13557] add warnings to all the commands that take long-term exclusive locks Created: 01/Apr/20  Updated: 30/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Carl Champain (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: execution, locking, locks
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-47032 Long running exclusive locks can end ... Closed
Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769

 Description   

Description

Add warnings to all the commands that take long-term exclusive locks (e.g., convertToCapped): the admin should take steps to reduce the volume of reads/writes going to locked things to avoid exhaustion of tickets, connections, or even threads. Long-term exclusive locks can cause the blocking of operations on not locked databases.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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