Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-8209

Exchange worker busy-spins after ForceRebalanceExchangeTask

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Currently, we assign timeout=0 if exchange worker receives ForceRebalanceExchangeTask, however, assignment back to non-zero value is performed only if rebalance is finished, which results in exchange worker busy-spin.

      Looks like we should re-assign timeout back to network timeout if timeout is zero and the queue is empty.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              agoncharuk Alexey Goncharuk
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: