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

Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/11/17 10:11:59 UTC

[jira] [Updated] (IGNITE-2975) Load balancer does not survive client reconnect

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

Vladimir Ozerov updated IGNITE-2975:
------------------------------------
    Fix Version/s:     (was: 1.8)
                   2.0

> Load balancer does not survive client reconnect
> -----------------------------------------------
>
>                 Key: IGNITE-2975
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2975
>             Project: Ignite
>          Issue Type: Bug
>          Components: compute
>    Affects Versions: 1.5.0.final
>            Reporter: Valentin Kulichenko
>             Fix For: 2.0
>
>
> {{RoundRobinGlobalLoadBalancer}} has a snapshot of nodes ({{nodeList}}) which is updated on each discovery event. But when the client reconnects after the full topology restart, the snapshot is not updated and it contains only nodes that already failed. {{EVT_CLIENT_NODE_DISCONNECTED}} and {{EVT_CLIENT_NODE_RECONNECTED}} should be properly handled.
> Other load balancing SPIs should be also checked.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)