[SERVER-13457] Not all rsMgr log messages start with "replSet" Created: 02/Apr/14  Updated: 10/Dec/14  Resolved: 14/Aug/14

Status: Closed
Project: Core Server
Component/s: Logging, Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Kevin Pulo Assignee: Alex Grover
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-5092 Better named logging with tracing Closed
Operating System: ALL
Participants:

 Description   

It is useful when analysing a logfile to search for "replSet" (case sensitively) to see the main replset related events. None of the following messages in db/repl/manager.cpp are found by these searches:

  • "another primary seen with election time"
  • "stepping down; another primary seen in replicaset"
  • "stepping down; another primary was elected more recently"
  • "another PRIMARY detected but it should step down since it was elected earlier than me"
  • log() << "stepping down " << primary->fullName() << " (priority " << ...
  • log() << "replset error could not reach/authenticate against any members" << endl;
  • log() << "auth problems, relinquishing primary" << rsLog;
  • log() << "can't see a majority of the set, relinquishing primary" << rsLog;
    Despite this, all are important events in the lifecycle of a replica set that are logged at the default logging level.


 Comments   
Comment by Eric Milkie [ 14/Aug/14 ]

This issue is fixed by the recent logging enhancements that label every log message with a component, such as REPLSET, for easy searchability.

Comment by Daniel Pasette (Inactive) [ 02/Apr/14 ]

The eventual fix for this is here: SERVER-5092. But the log msgs could be individually fixed up with little effort.

Generated at Thu Feb 08 03:31:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.