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

rs.printSlaveReplicationInfo() syncedTo field displays the epoch for unreachable secondaries

XMLWordPrintableJSON

    • Fully Compatible
    • Repl 2020-09-07, Repl 2020-09-21

      A secondary in a 3-node replica set was terminated; the primary kept taking writes, and rs.printSlaveReplicationInfo() would show something like this in 2.6.10:

      replset:PRIMARY> rs.printSlaveReplicationInfo()
source: skye.local:27018
        syncedTo: Fri Aug 07 2015 11:38:46 GMT-0400 (EDT)
        0 secs (0 hrs) behind the primary 
source: skye.local:27019
        syncedTo: Fri Aug 07 2015 11:37:17 GMT-0400 (EDT)
        89 secs (0.02 hrs) behind the primary

      The secondary in 27018 is caught up, and the one in 27019 is behind the primary as expected, since it was terminated a minute and a half ago.

      In 3.0.5 and 3.1.6 however:

      replset:PRIMARY> rs.printSlaveReplicationInfo()
source: skye.local:27018
    syncedTo: Fri Aug 07 2015 11:38:46 GMT-0400 (EDT)
    102 secs (0.03 hrs) behind the primary 
source: skye.local:27019
    syncedTo: Wed Dec 31 1969 19:00:00 GMT-0500 (EST)
    1438962028 secs (399711.67 hrs) behind the primary

      Note how the syncedTo date goes back to the epoch.

            Assignee:
            huayu.ouyang@mongodb.com Huayu Ouyang
            Reporter:
            ramon.fernandez@mongodb.com Ramon Fernandez Marina
            Votes:
            1 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: