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

Replica set‘’s secondary memeber's optimeData sometimes does not update

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • 3.4.13
    • Replication
    • None
    • ALL

    Description

      I have a replica set deployed, Primary, Secondary, Arbiter.
      and secondary server is deployed in an unstable server, sometimes, if the secondary server is stuck and down, . after the unstable server and mongo is resumed automatically, the optimeData(data) is no longer to sync Primary's optimeData(data), and the secondary mongo's all status looks good.
      please find attached log on secondary server, and rs.status

      Attachments

        1. primary.log
          12.07 MB
        2. rs.printSlaveReplicationInfo.JPG
          rs.printSlaveReplicationInfo.JPG
          18 kB
        3. rs.status1.JPG
          rs.status1.JPG
          77 kB
        4. rs.status2.JPG
          rs.status2.JPG
          92 kB
        5. secondary.log
          36.22 MB

        Activity

          People

            kelsey.schubert@mongodb.com Kelsey Schubert
            kenyang001 ken
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: