Re: [2.11.0]: 'B+Tree is corrupted' exception in GridCacheTtlManager.expire() and PartitionsEvictManager$PartitionEvictionTask.run() on node start

Hello Denis, * Yes, we run 2.11.0 against the old 2.8.1 PDS. * And no, it's not necessarily the compatibility problem since corruption was detected both in cache with and without old records. But yes, caches were created by 2.8.1 version. * I also forget to say that we did yet another test before

Re: [2.11.0]: 'B+Tree is corrupted' exception in GridCacheTtlManager.expire() and PartitionsEvictManager$PartitionEvictionTask.run() on node start

Hello, Zhenya 26.11.2021 12:32, Zhenya Stanilovsky пишет: > probably this is the > case: https://issues.apache.org/jira/browse/IGNITE-15990 > >   Thanks for pointing!  I also noticed this one. I investigate more and suspect that it can be the

Re: [2.11.0]: 'B+Tree is corrupted' exception in GridCacheTtlManager.expire() and PartitionsEvictManager$PartitionEvictionTask.run() on node start

probably this is the case:  https://issues.apache.org/jira/browse/IGNITE-15990       > >Hello Denis, >Yes, as I said in the original message we do use the expiration on persistent >caches. >The corruptedPages_2021-11-08_11-03-21_999.txt and >corruptedPages_2021-11-09_12-43-12_449.txt files were

Re: [2.11.0]: 'B+Tree is corrupted' exception in GridCacheTtlManager.expire() and PartitionsEvictManager$PartitionEvictionTask.run() on node start

Hi Sergey! Thank you for providing details. Have I understood correctly that you run newer version of Ignite on older persistent files? Is there any possibility that some data in your caches survived that 5 days of cluster work? I'm just trying to exclude any compatibility problems, like

Re: [2.11.0]: 'B+Tree is corrupted' exception in GridCacheTtlManager.expire() and PartitionsEvictManager$PartitionEvictionTask.run() on node start

Hi Sergey! Seems that the root cause of your problem is possible corruption of data page Caused by: java.lang.IllegalStateException: Item not found: 3 at org.apache.ignite.internal.processors.cache.persistence.tree.io.AbstractDataPageIO.findIndirectItemIndex(AbstractDataPageIO.java:476) and it