Hi,
Sorry, I missed this conversation. To understand your problem you should
provide the reproducer, cache configuration or steps how we can reproduce it
or file the issue with all this information.
At the moment it's not cleared how to solve it.
BR,
Andrei
--
Sent from:
Hi,
We have received Runtime failure on bounds again in 2 days. I am using
ignite 2.6 and started all nodes from scratch ( removed existing data).
error below
[7/21/18 13:22:43:031 UTC] 008f
E Critical system error detected
Hi,
I am out of context what you do in your code. However, I know that several
page corruption issues were fixed in 2.6 release.
So there is no specific suggestion from my side.
BR,
Andrei
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Andrei,
Yes, I have stopped all the servers and removed corrupted nodes data and
upgraded to 2.6 and restart the server.
any more suggestion and configuration changes to prevent this issue.
Thanks & Regards,
Venkat
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
In case if you see (page content is corrupted) and after that upgrade your
version to 2.6 then it's possible that your persistence is still broken.
The most simple way here is cleaning your PDS (work/db) directory before the
upgrading to 2.6.
In case if data is important then you also can
Hi Team,
We are receiving Runtime failure on bounds even after updating it to 2.6
version.
We used to receive Failed to get page IO instance (page content is
corrupted) from 2.3, 2.4 and 2.5, now in 2.6 it is changed to Item not
found: 1.
Till now we are in test environments but we
