Hi, We've found and fixed few issues related to ExpiryPolicy usage. Most likely, your issue is [1] and it is planned to ignite 2.6 release.
[1] https://issues.apache.org/jira/browse/IGNITE-8659 On Fri, Jun 22, 2018 at 8:43 AM Olexandr K <olexandr.kundire...@gmail.com> wrote: > Hi Team, > > Issue is still there in 2.5.0 > > Steps to reproduce: > 1) start 2 servers + 2 clients topology > 2) start load testing on client nodes > 3) stop server 1 > 4) start server 1 > 5) stop server 1 again when rebalancing is in progress > => and we got data corrupted here, see error below > => we were not able to restart Ignite cluster after that and need to > perform data folders cleanup... > > 2018-06-21 11:28:01.684 [ttl-cleanup-worker-#43] ERROR - Critical system > error detected. Will be handled accordingly to configured handler > [hnd=class o.a.i.failure.StopNodeOrHaltFailureHandler, > failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, err=class > o.a.i.IgniteException: Runtime failure on bounds: [lower=null, > upper=PendingRow []]]] > org.apache.ignite.IgniteException: Runtime failure on bounds: [lower=null, > upper=PendingRow []] > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:971) > ~[ignite-core-2.5.0.jar:2.5.0] > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:950) > ~[ignite-core-2.5.0.jar:2.5.0] > at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1024) > ~[ignite-core-2.5.0.jar:2.5.0] > at > org.apache.ignite.internal.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:197) > ~[ignite-core-2.5.0.jar:2.5.0] > at > org.apache.ignite.internal.processors.cache.GridCacheSharedTtlCleanupManager$CleanupWorker.body(GridCacheSharedTtlCleanupManager.java:137) > [ignite-core-2.5.0.jar:2.5.0] > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) > [ignite-core-2.5.0.jar:2.5.0] > at java.lang.Thread.run(Thread.java:748) [?:1.8.0_162] > Caused by: java.lang.IllegalStateException: Item not found: 2 > at > org.apache.ignite.internal.processors.cache.persistence.tree.io.AbstractDataPageIO.findIndirectItemIndex(AbstractDataPageIO.java:341) > ~[ignite-core-2.5.0.jar:2.5.0] > at > org.apache.ignite.internal.processors.cache.persistence.tree.io.AbstractDataPageIO.getDataOffset(AbstractDataPageIO.java:450) > ~[ignite-core-2.5.0.jar:2.5.0] > at > org.apache.ignite.internal.processors.cache.persistence.tree.io.AbstractDataPageIO.readPayload(AbstractDataPageIO.java:492) > ~[ignite-core-2.5.0.jar:2.5.0] > at > org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:150) > ~[ignite-core-2.5.0.jar:2.5.0] > at > org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:102) > ~[ignite-core-2.5.0.j > > BR, Oleksandr > > On Thu, Jun 14, 2018 at 2:51 PM, Olexandr K <olexandr.kundire...@gmail.com > > wrote: > >> Upgraded to 2.5.0 and didn't get such error so far.. >> Thanks! >> >> On Wed, Jun 13, 2018 at 4:58 PM, dkarachentsev < >> dkarachent...@gridgain.com> wrote: >> >>> It would be better to upgrade to 2.5, where it is fixed. >>> But if you want to overcome this issue in your's version, you need to add >>> ignite-indexing dependency to your classpath and configure SQL indexes. >>> For >>> example [1], just modify it to work with Spring in XML: >>> <property name="indexedTypes"> >>> <list> >>> <value>org.your.KeyObject</value> >>> <value>org.your.ValueObject</value> >>> </list> >>> </property> >>> >>> [1] >>> >>> https://apacheignite-sql.readme.io/docs/schema-and-indexes#section-registering-indexed-types >>> >>> Thanks! >>> -Dmitry >>> >>> >>> >>> -- >>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >>> >> >> > -- Best regards, Andrey V. Mashenkov
