[DOCS-11247] Docs for SERVER-28923: Add diagnosability and supportability features for retryable writes Created: 24/Jan/18  Updated: 29/Oct/23  Resolved: 12/Jun/18

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 3.7.2, 3.6.3

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: PM-257, serverstatus, transactions
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.mongodb.com/manual/reference/command/serverStatus/


Issue Links:
Documented
documents SERVER-28923 Add diagnosability and supportability... Closed
Participants:
Days since reply: 5 years, 35 weeks, 1 day ago
Epic Link: DOCS: 4.0 Server
Story Points: 0.8

 Description   

Documentation Request Summary:

This ticket added a new section to the serverStatus response called "transactions" that contains 3 new fields:

  • "retriedCommandsCount"
    • The total number of received write commands with statements that have already been executed, across all sessions
  • "retriedStatementsCount"
    • The total number of received statements that have already been executed, across all sessions
  • "transactionsCollectionWriteCount"
    • The total number of writes to the config.transactions collection, triggered when a new retryable write statement is committed. For updates and deletes there is one write per statement, but there is only one per batch of documents inserted, except when there is a failure that leads to each document being inserted separately.

"retriedCommandsCount" and "retriedStatementsCount" both ignore any retryable writes that may happen internally as part of a chunk migration, but "transactionsCollectionWriteCount" does include writes to a server's config.transactions collection that occur as part of a migration.

All three are NumberLongs.

Scope of changes:

  • serverStatus (backport to 3.6)
  • retryable writes (backport to 3.6)

Impact to other docs outside of this product:

none

MVP:

Resources:

Engineering Ticket Description:

This ticket is a placeholder to figure out between ourselves and with TSE what supportability and diagnosability enhancements we might need to include for retryable writes.

Things that come to mind include:

  • FTDC metrics for number of active sessions
  • Metrics for the CPU (and if possible I/O) overhead of maintaining the retryability metadata
  • Metrics for number of writes which have been retried
  • If we end up with a cache, metrics for hit-rate


 Comments   
Comment by Githook User [ 12/Jun/18 ]

Author:

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

Message: DOCS-11247: serverStatus.transactions
Branch: v3.6
https://github.com/mongodb/docs/commit/d2d08060966af312b9d527a66621f8cf1c6e68b2

Comment by Githook User [ 12/Jun/18 ]

Author:

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

Message: DOCS-11247: serverStatus.transactions
Branch: master
https://github.com/mongodb/docs/commit/7a113949b74aec592b6aab057d20667c29f4d451

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