[DOCS-12634] Docs for SERVER-40105: Improve diagnostic information in currentOp for excessive write conflicts and prepare conflicts Created: 15/Apr/19  Updated: 13/Nov/23  Resolved: 03/Jun/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.11, 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: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-40105 Improve diagnostic information in cur... Closed
Participants:
Days since reply: 4 years, 37 weeks ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

The top-level fields 'writeConflicts' and 'prepareReadConflicts' are now present in the currentOp() output.

The number of write conflicts represents the number of times a write attempt conflicted with another operation on the same document.

The number of prepare conflicts represents the number of times the operation blocked waiting for a write by a prepared transaction to commit or abort. An operation blocked on prepare conflicts holds both locks and storage engine resources while waiting.

Engineering Ticket Description:

Currently, when a non-transactional write conflicts with an active transaction, that write may keep retrying thousands of times until the transaction finally commits or aborts. This situation is hard to diagnose, because currentOp doesn't show that the active non-transactional writes have occurred so many retries.

Changes made by this ticket:
The top-level fields 'writeConflicts' and 'prepareReadConflicts' are now present in the currentOp() output.

The number of write conflicts represents the number of times a write attempt conflicted with another operation on the same document.

The number of prepare conflicts represents the number of times the operation blocked waiting for a write by a prepared transaction to commit or abort. An operation blocked on prepare conflicts holds both locks and storage engine resources while waiting.

Scope of changes

  • currentOp command and $currentOp pipeline stage
  • 4.2 rel notes
  • link in transactions considerations page.

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Githook User [ 29/May/19 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'Kay Kim', 'username': 'kay-kim'}

Message: DOCS-12634: 4.2 currentOp conflict metrics
Branch: master
https://github.com/mongodb/docs/commit/8ee807f348ccd9dc803105868274080c8b84c288

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