[
https://issues.apache.org/jira/browse/IGNITE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549150#comment-16549150
]
Stanilovsky Evgeny edited comment on IGNITE-8719 at 7/19/18 11:25 AM:
----------------------------------------------------------------------
also, index creation can be crashed independently, for example with Error
during parallel index create/rebuild.
{code:java}
IgniteChackedException: maximum of retries 1000 reached.
at
org.apache.ignite.internal.processors.cache.persistence.tree.BplusTree$Get.checkLockRetry(BPlusTree.java:2565)
{code}
was (Author: zstan):
also, index creation can be crashed independently, for example with Error
during parallel index create/rebuild.
IgniteChackedException: maximum of retries 1000 reached.
at
org.apache.ignite.internal.processors.cache.persistence.tree.BplusTree$Get.checkLockRetry(BPlusTree.java:2565)
> 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
>
>
> 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
(v7.6.3#76005)
