[
https://issues.apache.org/jira/browse/IGNITE-8723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-8723:
--------------------------------------
Fix Version/s: (was: 2.9)
2.10
> 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
> Priority: Major
> Fix For: 2.10
>
>
> 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
(v8.3.4#803005)
