You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Kalashnikov (JIRA)" <ji...@apache.org> on 2018/04/04 08:57:00 UTC
[jira] [Commented] (IGNITE-8048) Dynamic indexes are not stored to
cache data on node join
[ https://issues.apache.org/jira/browse/IGNITE-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425212#comment-16425212 ]
Anton Kalashnikov commented on IGNITE-8048:
-------------------------------------------
TC - [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&tab=projectOverview&branch_IgniteTests24Java8=pull%2F3719%2Fhead]
> Dynamic indexes are not stored to cache data on node join
> ---------------------------------------------------------
>
> Key: IGNITE-8048
> URL: https://issues.apache.org/jira/browse/IGNITE-8048
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 2.4
> Reporter: Alexey Goncharuk
> Assignee: Anton Kalashnikov
> Priority: Major
> Fix For: 2.5
>
> Attachments: IgniteDynamicIndexRestoreTest.java
>
>
> Consider the following scenario:
> 1) Start nodes, add some data
> 2) Shutdown a node, create a dynamic index
> 3) Shutdown the whole cluster, startup with the absent node, activate from the absent node
> 4) Since the absent node did not 'see' the create index, index will not be active after cluster activation
> 5) Update some data in the cluster
> 6) Restart the cluster, but activate from the node which did 'see' the create index
> 7) Attempt to update data. Depending on the updates in (5), this will either hang or result in an exception
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)