ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Gura (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-3209) Need to wait for affinity assignment change during affinityCall failover
Date Wed, 15 Jun 2016 15:07:09 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331890#comment-15331890
] 

Andrey Gura edited comment on IGNITE-3209 at 6/15/16 3:06 PM:
--------------------------------------------------------------

Fixed and merged into master branch.


was (Author: agura):
Merged into master branch.

> 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)

Mime
View raw message