[DOCS-12197] Docs for SERVER-32906: Improve logging around elections Created: 13/Nov/18  Updated: 13/Nov/23  Resolved: 14/Nov/18

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

Issue Links:
Documented
documents SERVER-32906 Improve logging around elections Closed
Participants:
Days since reply: 5 years, 13 weeks ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

"replication.election" is a child of "replication" (like "replication.rollback", for instance)

Engineering Ticket Description:

To aide diagnosing test failures, we should add logging any time we take an election-related action (election timeout expiring, calling for an election, voting in an election, etc), with all possible inputs to that decision (dump of heartbeat and spanning tree liveness tables, etc.).

This could be done with a new log sub-component, so that we can have higher verbosity in our tests than in prod.

Scope of changes

  • source/reference/log-messages.txt
  • source/reference/method/db.getLogComponents.txt (setLogComponent and parameters has examples – but not specific ones)
  • source/includes/options-conf.yaml
  • source/includes/list-log-component-setting-correspondence.rst
  • source/reference/configuration-options.txt
  • 4.2 rel notes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Githook User [ 14/Nov/18 ]

Author:

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

Message: DOCS-12197: ELECTION log component
Branch: master
https://github.com/mongodb/docs/commit/274fcfbb5afe44c6a2e24421160c7ce281278d04

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