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

schedule only one outstanding liveness item of work

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • 3.2.0-rc2
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl B (10/30/15)

      When we schedule a liveness update in replication, we need to make sure there aren't any outstanding updates already scheduled – otherwise, they will leak and continue to reschedule themselves forever.

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: