schedule only one outstanding liveness item of work

XMLWordPrintableJSON

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

      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:
              Eric Milkie
              Reporter:
              Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: