[
https://issues.apache.org/jira/browse/IGNITE-17065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551097#comment-17551097
]
Yury Gerzhedovich commented on IGNITE-17065:
--------------------------------------------
[~liyuj] , is itpossible to reproduce the issue on last 2.13 version of Ignite?
Since 2.10 were fixed many B+tree corrupt issues and probably the issue is not
actual. Also to have ability to analyze such type of issue requires WAL and PDS
files. Could you please attache WAL and PDS?
List (not full) of possible root cause fixed issues :
https://issues.apache.org/jira/browse/IGNITE-16494
https://issues.apache.org/jira/browse/IGNITE-15943
https://issues.apache.org/jira/browse/IGNITE-12911
https://issues.apache.org/jira/browse/IGNITE-15990
https://issues.apache.org/jira/browse/IGNITE-16661
> CorruptedTreeException: B+Tree is corrupted(Duplicate row in index)
> -------------------------------------------------------------------
>
> Key: IGNITE-17065
> URL: https://issues.apache.org/jira/browse/IGNITE-17065
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.10
> Reporter: YuJue Li
> Priority: Major
> Attachments: 2021-12-21_13-59-27.574.log
>
>
> In a pure memory cluster, the B+Tree is corrupted during node restart.
> See the attachment log for details.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
