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

Posted to issues@ignite.apache.org by "Maxim Muzafarov (JIRA)" <ji...@apache.org> on 2018/07/04 12:55:00 UTC

[jira] [Commented] (IGNITE-7514) Affinity assignment isn't recalculated if PRIMARY node isn't OWNER

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

Maxim Muzafarov commented on IGNITE-7514:
-----------------------------------------

No PR desctiption attached to issue.
Merged commit is supposed to be:

https://github.com/apache/ignite/commit/faf50f1dad74028f6cd665ec23ee3dabc40ea923

> Affinity assignment isn't recalculated if PRIMARY node isn't OWNER
> ------------------------------------------------------------------
>
>                 Key: IGNITE-7514
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7514
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.4
>            Reporter: Ilya Lantukh
>            Assignee: Alexey Goncharuk
>            Priority: Major
>             Fix For: 2.5
>
>
> It can happen after activation or recovery and leads to multiple exceptions / assertions during cache operations mapping.



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