ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanislav Lukyanov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8719) Index left partially built if a node crashes during index create or rebuild
Date Tue, 24 Jul 2018 10:57:00 GMT

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

Stanislav Lukyanov commented on IGNITE-8719:

There is a similar issue with an empty index tree being persisted. I can reproduce it by shutting
node down forcibly (kill -9 or taskkill /f), but I guess the key is in shutting down in the
middle of checkpoint or something like that. The reproducer is attached: [^IndexRebuildingTest.java].

> 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
>            Assignee: Dmitriy Sorokin
>            Priority: Critical
>             Fix For: 2.7
>         Attachments: IndexRebuildingTest.java
> Currently, we do not have any state associated with the index tree. Consider the following
> 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

View raw message