[SERVER-26914] improve log messages for freshness checking Created: 04/Nov/16  Updated: 05/Apr/17  Resolved: 23/Jan/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.2.10, 3.4.0-rc2
Fix Version/s: 3.2.13, 3.4.3, 3.5.2

Type: Improvement Priority: Minor - P4
Reporter: Benety Goh Assignee: Judah Schvimer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4, v3.2
Sprint: Repl 2017-01-23, Repl 2017-02-13
Participants:
Linked BF Score: 0

 Description   

This came up while debugging an intermittent failure in jstests/multiVersion/mixed_storage_version_replication.js.

It would be useful to know which node is fresher than the candidate.

[js_test:mixed_storage_version_replication] 2016-10-26T04:13:29.478+0000 d20510| 2016-10-26T04:13:29.467+0000 I REPL     [conn58] replSetReconfig admin command received from client
...
[js_test:mixed_storage_version_replication] 2016-10-26T04:13:29.482+0000 d20510| 2016-10-26T04:13:29.479+0000 I REPL     [ReplicationExecutor] Stepping down self (priority 3) because ip-10-41-142-26:20512 has higher priority 4 and is only 2 seconds behind me
...
[js_test:mixed_storage_version_replication] 2016-10-26T04:13:29.491+0000 d20510| 2016-10-26T04:13:29.484+0000 I REPL     [replExecDBWorker-1] transition to SECONDARY
...
[js_test:mixed_storage_version_replication] 2016-10-26T04:13:29.509+0000 d20512| 2016-10-26T04:13:29.492+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Successfully connected to ip-10-41-142-26:20510
[js_test:mixed_storage_version_replication] 2016-10-26T04:13:29.509+0000 d20512| 2016-10-26T04:13:29.492+0000 I REPL     [ReplicationExecutor] Requesting that ip-10-41-142-26:20510 (priority 3) step down because I have higher priority 4 and am only 0 seconds behind it
...
[js_test:mixed_storage_version_replication] 2016-10-26T04:13:29.510+0000 d20512| 2016-10-26T04:13:29.493+0000 I REPL     [ReplicationExecutor] Member ip-10-41-142-26:20510 is now in state SECONDARY
[js_test:mixed_storage_version_replication] 2016-10-26T04:13:29.510+0000 d20512| 2016-10-26T04:13:29.493+0000 I REPL     [ReplicationExecutor] Standing for election
...
[js_test:mixed_storage_version_replication] 2016-10-26T04:13:29.511+0000 d20512| 2016-10-26T04:13:29.493+0000 I REPL     [ReplicationExecutor] not electing self, we are not freshest
[js_test:mixed_storage_version_replication] 2016-10-26T04:13:29.511+0000 d20512| 2016-10-26T04:13:29.493+0000 I REPL     [ReplicationExecutor] not electing self, we are not freshest



 Comments   
Comment by Githook User [ 06/Feb/17 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-26914 improve log messages for freshness checking

(cherry picked from commit 7480e053bb992f869bf83c8e54ee088afa199bb9)
Branch: v3.2
https://github.com/mongodb/mongo/commit/071508878c4e715a0828e75410fa2ecb3471dee0

Comment by Githook User [ 06/Feb/17 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-26914 improve log messages for freshness checking

(cherry picked from commit 7480e053bb992f869bf83c8e54ee088afa199bb9)
Branch: v3.4
https://github.com/mongodb/mongo/commit/2f7849eef7a168fbc9c357e7fd61d95d9f19b5c0

Comment by Githook User [ 23/Jan/17 ]

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-26914 improve log messages for freshness checking
Branch: master
https://github.com/mongodb/mongo/commit/7480e053bb992f869bf83c8e54ee088afa199bb9

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