Re: And again... Failed to get page IO instance (page content is corrupted)

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:

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.mashen...@gmail.com> wrote: > Hi Oleg, > > Yes, page corruption issues shouldn't happened when persistence is > disabled. > Please, let us know

Re: And again... Failed to get page IO instance (page content is corrupted)

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 wrote: > Hi Andrey, > > Thanks for clarifying this. > We have just a single persistent cache and I reworked the code to

Re: And again... Failed to get page IO instance (page content is corrupted)

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]

Re: And again... Failed to get page IO instance (page content is corrupted)

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

Re: And again... Failed to get page IO instance (page content is corrupted)

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 wrote: > Hi Team, > > Issue is still there in 2.5.0 > >

Re: And again... Failed to get page IO instance (page content is corrupted)

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

Re: And again... Failed to get page IO instance (page content is corrupted)

Upgraded to 2.5.0 and didn't get such error so far.. Thanks! On Wed, Jun 13, 2018 at 4:58 PM, dkarachentsev 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

Re: And again... Failed to get page IO instance (page content is corrupted)

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:

Re: And again... Failed to get page IO instance (page content is corrupted)

I'm using key/value API. Should I define index for the key explicitly? This sounds strange... Can you give a sample how I can do this in xml please? Here is one of my cache configurations. Actually I'm storing UUID per UUID here: IgniteCache

Re: And again... Failed to get page IO instance (page content is corrupted)

Hi, Possibly, it is a bug in partition eviction optimization. Ignite can skip partition eviction procedure and remove partition instantly if there is no indexes. If it is so, you can try the latest ignite-2.5 version [1] or as a workaround you can add index via configuring QueryEntity or via

Re: And again... Failed to get page IO instance (page content is corrupted)

Hi guys, I got similar errors in 2.4.0 First: org.apache.ignite.IgniteException: Runtime failure on bounds: [lower=null, upper=PendingRow []] --> Caused by: java.lang.IllegalStateException: Failed to get page IO instance (page content is corrupted) Then lots of:

Re: And again... Failed to get page IO instance (page content is corrupted)

Hello Sergey! Cross-posting from a different thread, the underlying problem could be fixed in 2.4: https://issues.apache.org/jira/browse/IGNITE-7278 Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: And again... Failed to get page IO instance (page content is corrupted)

Sergey, Arseny, We've fixed a number of similar issues in 2.4 Ignite version. However, this one, ExpiryPolicy with persistence still buggy. Here is a ticket for it [1]. The ticket has a PR that should fix this issue, but it broke backward compatibility as TTLManager, who responsible for expired

Re: And again... Failed to get page IO instance (page content is corrupted)

Hi, Arseny We are using ext4 with defaults,noatime,lazytime options on Virtuozzo Linux release 7.3. We have refactored parts of logic and abandoned the use of any expired policies(( On Thu, Mar 15, 2018 at 7:34 PM, Arseny Kovalchuk < arseny.kovalc...@synesis.ru> wrote: > Hi guys. > > I've

Re: And again... Failed to get page IO instance (page content is corrupted)

Hi guys. I've got a reproducer that can be related. See comments http://apache-ignite-users.70518.x6.nabble.com/Partition-eviction-failed-this-can-cause-grid-hang-Caused-by-java-lang-IllegalStateException-Failed--tp19122p20524.html Sergey Sergeev, just for reference, what kind of file system do

Re: And again... Failed to get page IO instance (page content is corrupted)

Hi Mikhail, Unfortunately, the problem has repeated itself on ignite-core-2.3.3 27.02.18 00:27:55 ERROR GridCacheIoManager - Failed to process message [senderId=8f99c887-cd4b-4c38-a649-ca430040d535, messageType=class o.a.i.i.processors.cache.distributed.dht.atomic. GridNearAtomicUpdateResponse]

Re: And again... Failed to get page IO instance (page content is corrupted)

Hi Sergey, The 2.4 release is about to be voted for. You can use the RC1 in the mean time: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-4-0-RC1-td27687.html D. On Mon, Feb 19, 2018 at 6:43 AM, Mikhail wrote: > Hi Sergey, > > The

Re: And again... Failed to get page IO instance (page content is corrupted)

Hi Sergey, The release of 2.4 should be soon, in a week or couple, however, there's no strong schedule for Apache releases. Could you please share a reproducer for the issue? Might be you can share a storage on which the issue can be reproduced? Thanks, Mike. -- Sent from:

And again... Failed to get page IO instance (page content is corrupted)

Hi Igniters I can't defeat the bug. It is reproducing on ignite version community 2.3.0 and on trial professional 2.3.2 editions. The Cache has configuration like: final CacheConfiguration cacheConfiguration = new CacheConfiguration<>(getEntityClass().getSimpleName());