Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.6.16
    • Fix Version/s: None
    • Labels:
      None

      Description

      FLUSH_NOT_COMPLETED does not keep track of which FLUSH it was related to. FLUSH_COMPLETED only keeps track of whether the FLUSH was for the current view.

      If these responses are delayed (which can be caused by a long GC pause on the node sending it) where a new FLUSH has been started, these can be interpreted as responses for the wrong FLUSH.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dereed Dennis Reed
                  Reporter:
                  dereed Dennis Reed
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated: