[DOCS-16581] Investigate changes in SERVER-84440: Expose the number of replication waiters in serverStatus Created: 11/Jan/24 Updated: 22/Jan/24 Resolved: 19/Jan/24 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0, Server_Docs_[20240122] |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Matthew Maville |
| Resolution: | Done | Votes: | 0 |
| Labels: | feature | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| URL(s): | https://www.mongodb.com/docs/manual/reference/command/serverStatus/ | ||||||||
| Participants: | |||||||||
| Days since reply: | 3 weeks, 6 days ago | ||||||||
| Description |
|
Original Downstream Change Summary This adds two metrics to the serverStatus.metrics section:
repl.waiters.replication exposes how many threads are waiting for a replicated and/or journaled write concern to resolve. repl.waiters.opTime exposes how many threads are waiting for a local optime only. Description of Linked TicketThe replication waiters list can grow with the number of operations waiting for write concern. Advancing replication timestamps also requires updating all waiters in this list under a mutex. If the list is long, this can take a long time. It would be useful to be able to see how many operations are waiting for replication in this state, which would make it easier to diagnose problems in this area. |