[DOCS-13094] Investigate changes in SERVER-34722: Add new server status metrics about oplog application Created: 11/Oct/19  Updated: 13/Nov/23  Resolved: 02/Mar/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.7, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Jeffrey Allen
Resolution: Fixed Votes: 0
Labels: docs-grab-bag
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-34722 Add new server status metrics about o... Closed
Participants:
Days since reply: 3 years, 49 weeks ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

Added 5 server status metrics:
repl.syncSource.numSelections: The number of times a node attempted to choose a node to sync from among the available sync source options. This occurs if we re-evaluate our sync source, receive an error from the source, or step down.
repl.syncSource.numTimesChoseSame: The number of times a node kept it's original sync source after re-evaluating if its current sync source was optimal.
repl.syncSource.numTimesChoseDifferent: The number of times a node chose a new sync source after re-evaluating if its current sync source was optimal.
repl.syncSource.numTimesCouldNotFind: The number of times a node could not find a sync source when choosing a node to sync from among the available options.
repl.network.replSetUpdatePosition.num: The number of replSetUpdatePosition commands a node sent to its sync source.

Description of Linked Ticket

Ideas for improvements:
Counts of replSetUpdatePosition commands sent
Counts of heartbeats sent to each node
Counts of heartbeats received from each node
Counts getMores sent to sync source
Lag of the updatePositionLastAppliedOpTime that primaries use to commit oplog entries.
Count of elections run
Count of how often we choose a new sync source (even if it's the same one)
Liveness/state view of every other node in the replica set

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Githook User [ 04/Mar/20 ]

Author:

{'username': 'jeff-allen-mongo', 'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com'}

Message: (DOCS-13094): Adding new syncSource metrics to changelog
Branch: master
https://github.com/mongodb/docs/commit/2a0b55cbb9e537de820fda69bae7ed9bd03acc6b

Comment by Githook User [ 02/Mar/20 ]

Author:

{'username': 'jeff-allen-mongo', 'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com'}

Message: (DOCS-13094): Adding new syncSource metrics to serverStatus
Branch: master
https://github.com/mongodb/docs/commit/57ca86335ead9893a888c9729a39bd1af6b8df77

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