Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-26914

improve log messages for freshness checking

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Minor - P4
    • Resolution: Fixed
    • 3.2.10, 3.4.0-rc2
    • 3.2.13, 3.4.3, 3.5.2
    • Replication
    • None
    • Fully Compatible
    • v3.4, v3.2
    • Repl 2017-01-23, Repl 2017-02-13
    • 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
      

      Attachments

        Activity

          People

            judah.schvimer@mongodb.com Judah Schvimer
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: