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/01/25 14:09: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=16339248#comment-16339248 ]
Alexey Goncharuk commented on IGNITE-7514:
------------------------------------------
Ilya, I reverted this change and reopened the ticket because the commit breaks tests:
ClusterStatePartitionedSelfTest.testActivationFromClient
ClusterStatePartitionedSelfTest.testNoRebalancing
> 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: Ilya Lantukh
> Priority: Major
> Fix For: 2.4
>
>
> 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)