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

Possible bug in primary's tracking of how up-to-date its secondaries are.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 2.4.0-rc0
    • Replication
    • None
    • ALL

    Description

      It seems possible in some cases for the optimes reported in a primary's local.slaves collection to differ from the optimes reported by replSetGetStatus. This can cause problems if the primary tries to wait for all secondaries to be caught up in replication.

      Attachments

        Activity

          People

            milkie@mongodb.com Eric Milkie
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: