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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.4.0-rc0
    • Component/s: Replication
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Eric Milkie
              Reporter:
              Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: