You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Olexandr K <ol...@gmail.com> on 2018/07/05 23:25:54 UTC
Re: And again... Failed to get page IO instance (page content is corrupted)
Hi guys,
are you still planning to release 2.6.0 as patch release for 2.5.0?
BR, Oleksandr
On Fri, Jun 29, 2018 at 11:43 AM, Andrey Mashenkov <
andrey.mashenkov@gmail.com> wrote:
> Hi Oleg,
>
> Yes, page corruption issues shouldn't happened when persistence is
> disabled.
> Please, let us know it you will face one.
>
>
> On Fri, Jun 29, 2018 at 1:56 AM Olexandr K <ol...@gmail.com>
> wrote:
>
>> Hi Andrey,
>>
>> Thanks for clarifying this.
>> We have just a single persistent cache and I reworked the code to get rid
>> of expiration policy.
>> All our non-persistent caches have expiration policy but this should not
>> be a problem, right?
>>
>> BR, Oleksandr
>>
>> On Thu, Jun 28, 2018 at 8:37 PM, Andrey Mashenkov <
>> andrey.mashenkov@gmail.com> wrote:
>>
>>> Hi Oleg,
>>>
>>> The issue you mentioned IGNITE-8659 [1] is caused by IGNITE-5874 [2]
>>> that will not a part of ignite-2.6 release.
>>> For now, 'ExpiryPolicy with persistence' is totally broken and all it's
>>> fixes are planned to the next 2.7 release.
>>>
>>>
>>> [1] https://issues.apache.org/jira/browse/IGNITE-8659
>>> [2] https://issues.apache.org/jira/browse/IGNITE-5874
>>>
>>> On Tue, Jun 26, 2018 at 11:26 PM Olexandr K <
>>> olexandr.kundirenko@gmail.com> wrote:
>>>
>>>> Hi Andrey,
>>>>
>>>> I see Fix version 2.7 in Jira: https://issues.apache.org/
>>>> jira/browse/IGNITE-8659
>>>> This is a critical bug.. bouncing of server node in not-a-right-time
>>>> causes a catastrophe.
>>>> This mean no availability in fact - I had to clean data folders to
>>>> start my cluster after that
>>>>
>>>> BR, Oleksandr
>>>>
>>>>
>>>> On Fri, Jun 22, 2018 at 4:06 PM, Andrey Mashenkov <
>>>> andrey.mashenkov@gmail.com> wrote:
>>>>
>>>>> 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.kundirenko@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.kundirenko@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 <
>>>>>>> dkarachentsev@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
>>>>>
>>>>
>>>>
>>>
>>> --
>>> Best regards,
>>> Andrey V. Mashenkov
>>>
>>
>>
>
> --
> Best regards,
> Andrey V. Mashenkov
>
Re: And again... Failed to get page IO instance (page content is
corrupted)
Posted by "slava.koptilin" <sl...@gmail.com>.
Hello Oleksandr,
The ignite-2.6 branch is already stabilized and frozen.
I hope the voting will be opened today!
You can follow this topic to get updates on this.
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-2-6-emergency-release-suggestion-tc31340.html
Thanks!
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/