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

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2016/06/09 06:27:21 UTC

[jira] [Updated] (IGNITE-3209) Need to wait for affinity assignment change during affinityCall failover

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

Semen Boikov updated IGNITE-3209:
---------------------------------
    Assignee: Andrey Gura  (was: Valentin Kulichenko)

> Need to wait for affinity assignment change during affinityCall failover
> ------------------------------------------------------------------------
>
>                 Key: IGNITE-3209
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3209
>             Project: Ignite
>          Issue Type: Bug
>          Components: compute
>    Affects Versions: 1.6
>            Reporter: Valentin Kulichenko
>            Assignee: Andrey Gura
>             Fix For: 1.7
>
>
> {{AlwaysFailoverSpi.failover()}} method makes several attempts (5 by default) to get new primary node for the affinity key. Affinity assignment takes time, so there is a big chance to make all these attempts before new node is returned.
> We need to add discovery event that initiated failover to {{FailoverContext}} and wait for affinity is assigned.



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