Hi,
Could you please clarify what version of Ignite you're currently using?
Also can you attach full logs from all nodes and if it's possible provide
your persistence data for the cache with corrupted index tree ("
epro_model_abcd")?
By default Ii should be in ${IGNITE_HOME}/work/db/{node}/{cache} directory.
Regards,
Igor
On Fri, Sep 20, 2019 at 1:21 PM Shiva Kumar <[email protected]>
wrote:
> Hi all,
> I have deployed 3 node Ignite cluster with native persistence on
> Kubernetes and one of the node crashed with below error message,
>
> *org.h2.message.DbException: General error: "class
> org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
> Runtime failure on search row: Row@8cfe967[ key: epro_model_abcdKey
> [idHash=822184780, hash=737706081, NE_ID=, NAME=], val: epro_model_abcd
> [idHash=60444003, hash=1539928610, epro_ID=51, LONGITUDE=null,
> DELETE_TIME=null, VENDOR=null, CREATE_TIME=2019-09-19T20:38:32.361929Z,
> UPDATE_TIME=2019-09-19T20:40:05.821447Z, ADDITIONAL_INFO=null,
> VALID_UNTIL=2019-11-18T20:38:32.362036Z, TYPE=null, LATITUDE=null], ver:
> GridCacheVersion [topVer=180326822, order=1568925345552, nodeOrder=6] ][
> 51, 2019-09-19T20:38:32.361929Z, 2019-09-19T20:40:05.821447Z, null,
> 2019-11-18T20:38:32.362036Z, , , null, null, null, null, null ]"
> [50000-197]|*
>
> Please find attached file [index_corruption.txt] for complete backtrace.
>
> It looks like the Index got corrupted, I am not sure what exactly caused
> the index to corrupt. Any knows issues related to this?
>
> In my cluster, many applications write into many tables simultaneously and
> some queries run on many tables simultaneously and frequently application
> deletes unwanted rows[old data] in the tables using *delete from table*
> SQL operation.
>
>
