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

Update current known primary from command metadata

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.8
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • Repl 15 (06/03/16)
    • 0

      When we process the metadata from commands such as finds from the fetcher, the current primary index is included, however we don't do anything with the index once we get it. This information would fix the race between heartbeats updating metadata and the fetcher checking the validity of its sync source.

            Assignee:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: