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 2019/10/03 08:24:00 UTC

[jira] [Commented] (IGNITE-8719) Index left partially built if a node crashes during index create or rebuild

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

Maxim Muzafarov commented on IGNITE-8719:
-----------------------------------------

Folks,

This is a known issue and will be solved as a part of [IEP-28: Index rebuild|[https://cwiki.apache.org/confluence/display/IGNITE/IEP-28%3A+Cluster+peer-2-peer+balancing]] index rebuild procedure.

> Index left partially built if a node crashes during index create or rebuild
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-8719
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8719
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Alexey Goncharuk
>            Priority: Critical
>             Fix For: 2.8
>
>         Attachments: IndexRebuildAfterNodeCrashTest.java, IndexRebuildingTest.java
>
>
> Currently, we do not have any state associated with the index tree. Consider the following scenario:
> 1) Start node, put some data
> 2) start CREATE INDEX operation
> 3) Wait for a checkpoint and stop node before index create finished
> 4) Restart node
> Since the checkpoint finished, the new index tree will be persisted to the disk, but not all data will be present in the index.
> We should somehow store information about initializing index tree and mark it valid only after all data is indexed. The state should be persisted as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)