You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/06/06 14:01:00 UTC

[jira] [Created] (IGNITE-8723) Detect index corruption at runtime

Alexey Goncharuk created IGNITE-8723:
----------------------------------------

             Summary: Detect index corruption at runtime
                 Key: IGNITE-8723
                 URL: https://issues.apache.org/jira/browse/IGNITE-8723
             Project: Ignite
          Issue Type: Improvement
            Reporter: Alexey Goncharuk


Several times Ignite users faced a situation when SQL indexes were corrupted (linked to invalid or removed data).
I think it makes sense to slightly rework such errors during index dereference, and
1) Fail all ongoing and further SQL queries assigned to this node. SQL mapper should cache this and try to re-route SQL requests to other OWNING nodes
2) After index corruption is detected, all or only corrupted indexes should be deallocated (the decision depends on what is faster) and rebuilt
3) After indexes are rebuilt, we should notify other nodes that the node is available for queries again



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)