You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/04/10 17:41:00 UTC

[jira] [Updated] (IGNITE-8209) Exchange worker busy-spins after ForceRebalanceExchangeTask

     [ https://issues.apache.org/jira/browse/IGNITE-8209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Goncharuk updated IGNITE-8209:
-------------------------------------
    Labels: newbie  (was: )

> Exchange worker busy-spins after ForceRebalanceExchangeTask
> -----------------------------------------------------------
>
>                 Key: IGNITE-8209
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8209
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Goncharuk
>            Priority: Major
>              Labels: newbie
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)