Hi,
I don't see any mentions of OOM. Provided log message reports blocking
of db-checkpoint-thread. I think worker tries to acquire checkpoint
read lock.
Stack trace corresponds to the thread that detected blocking. Failure
handler prints out threads dump to the log. This thread dump can help
in
Hi,
How does the JVM error look like?
Apart from that, Andrey, Igniters, the failure handler fired off but I have
no glue from the shared logs what happened or how it is connected to the
Java heap issues. Should I expect to see anything from the logs not added
to the thread?
--
Denis Magda
On
If you have all tables colocated with each other, i.e. having the same
affinity function and backups count then you can try using cache groups -
https://apacheignite.readme.io/docs/cache-groups
--Yakov
пт, 29 мар. 2019 г. в 08:49, ashfaq :
> We are testing and also the production data would be
We are testing and also the production data would be so much.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Team,
We are installing ignite on kubernetes environment with native persistence
enabled. When we try to create around 400 tables using the sqlline end point
, the pods are restarting after creating 200 tables with jvm heap error so
we have increased the java heap size from 1GB to 2GB and
Hello!
Ignite has around 20M heap overhead per table, this means 6G for 300
tables. Why do you need so many tables?
Regards,
--
Ilya Kasnacheev
чт, 28 мар. 2019 г. в 14:47, ashfaq :
> Hi Team,
>
> We are installing ignite on kubernetes environment with native persistence
> enabled. When we
