producer thread can continue producing after a node becomes primary

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.0.5, 3.1.6
    • Affects Version/s: 3.0.1
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • RPL 6 07/17/15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      These ops are not thrown away and can lead to a deadlock between the applier and producer threads. The applier thread believes it has finished and is waiting for the producer thread to signal that it has paused. Meanwhile, the producer thread is waiting for the op that arrived late (which the applier is unaware of) to be applied.

            Assignee:
            Matt Dannenberg (Inactive)
            Reporter:
            Matt Dannenberg (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: