[SERVER-13068] Large number of cryptic log messages "replSet last" in rs_sync.cpp Created: 06/Mar/14  Updated: 11/Jul/16  Resolved: 17/Mar/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.6.0-rc0
Fix Version/s: 2.6.0-rc2

Type: Improvement Priority: Minor - P4
Reporter: Thomas Rueckstiess Assignee: Matt Dannenberg
Resolution: Done Votes: 2
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

In src/mongo/db/repl/rs_sync.cpp:966:

LOG(1) << "replSet last: " << slave->last.toString() << " to "

On loglevel 1, which is quite common, this creates a large number of cryptic log messages:

2014-03-06T13:17:43.811+1100 [rsSyncNotifier] replSet last: 5317dac6:5 to 5317dac7:1
2014-03-06T13:17:43.813+1100 [rsSyncNotifier] replSet last: 5317dac7:1 to 5317dac7:2
2014-03-06T13:17:43.815+1100 [rsSyncNotifier] replSet last: 5317dac7:2 to 5317dac7:5
2014-03-06T13:17:43.815+1100 [rsSyncNotifier] replSet last: 5317dac7:6 to 5317dac7:6
2014-03-06T13:17:43.818+1100 [rsSyncNotifier] replSet last: 5317dac7:6 to 5317dac7:9
2014-03-06T13:17:43.818+1100 [rsSyncNotifier] replSet last: 5317dac7:a to 5317dac7:a
2014-03-06T13:17:43.820+1100 [rsSyncNotifier] replSet last: 5317dac7:a to 5317dac7:d
2014-03-06T13:17:43.822+1100 [rsSyncNotifier] replSet last: 5317dac7:d to 5317dac7:f
2014-03-06T13:17:43.822+1100 [rsSyncNotifier] replSet last: 5317dac7:11 to 5317dac7:11
2014-03-06T13:17:43.824+1100 [rsSyncNotifier] replSet last: 5317dac7:11 to 5317dac7:13
2014-03-06T13:17:43.824+1100 [rsSyncNotifier] replSet last: 5317dac7:15 to 5317dac7:15
2014-03-06T13:17:43.826+1100 [rsSyncNotifier] replSet last: 5317dac7:15 to 5317dac7:19
2014-03-06T13:17:43.828+1100 [rsSyncNotifier] replSet last: 5317dac7:19 to 5317dac7:1c
2014-03-06T13:17:43.829+1100 [rsSyncNotifier] replSet last: 5317dac7:1d to 5317dac7:1d
2014-03-06T13:17:43.831+1100 [rsSyncNotifier] replSet last: 5317dac7:1d to 5317dac7:20
2014-03-06T13:17:43.831+1100 [rsSyncNotifier] replSet last: 5317dac7:21 to 5317dac7:21
2014-03-06T13:17:43.833+1100 [rsSyncNotifier] replSet last: 5317dac7:21 to 5317dac7:24
2014-03-06T13:17:43.835+1100 [rsSyncNotifier] replSet last: 5317dac7:24 to 5317dac7:26
2014-03-06T13:17:43.836+1100 [rsSyncNotifier] replSet last: 5317dac7:28 to 5317dac7:28
2014-03-06T13:17:43.838+1100 [rsSyncNotifier] replSet last: 5317dac7:28 to 5317dac7:2a

Can we explain these better, or alternatively raise the log level to 2 or 3 if they are not required for normal operational use?



 Comments   
Comment by Eric Milkie [ 18/Mar/14 ]

Turn on debug log level 1 and then do some writes with replication.

Comment by Jonathan Abrahams [ 18/Mar/14 ]

What are the steps to reproduce this?

Comment by Githook User [ 17/Mar/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-13068 remove other occurance of replset last message

(cherry picked from commit 8c11be20ca312e5507a5e4560d62d07010c60543)
Branch: v2.6
https://github.com/mongodb/mongo/commit/ff6d29cbf6cfde219afd5d5725eedf70cd7f834e

Comment by Githook User [ 17/Mar/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-13068 remove other occurance of replset last message
Branch: master
https://github.com/mongodb/mongo/commit/ecc00b5bfba8961e0884e591ba1866eeb0cb67ab

Comment by Matt Dannenberg [ 13/Mar/14 ]

Found another place that prints this message and needs to be fixed to be the new style.

Comment by Githook User [ 12/Mar/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-13068 improve log message in percolate() and increase its loglevel
Branch: master
https://github.com/mongodb/mongo/commit/9c3e4354416d5fbc6c8f4a27cb0d7c6310a55914

Comment by Thomas Rueckstiess [ 06/Mar/14 ]

Further review of the log file shows 368766 occurrences of this message in a 15 minute window. This makes logLevel 1 log files very difficult to process, so I recommend increasing the log level to 3 for this message.

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