Shiva,
What version of Ignite do you use?
Before version 2.7 Ignite used a different mechanism to limit the size of the
WAL history. It used DataStorageConfiguration#walHistorySize property, which is
currently deprecated. This is what’s explained on the internal documentation
page.
In Ignite v
Please share the whole log file. It might be the case that something goes
wrong with volumes you attached to Ignite pods.
-
Denis
On Thu, Aug 22, 2019 at 8:07 AM Shiva Kumar
wrote:
> Hi Denis,
>
> Thanks for your response,
> yes in our test also we have seen OOM errors and pod crash.
> so we w
Hi Denis,
Thanks for your response,
yes in our test also we have seen OOM errors and pod crash.
so we will follow the recommendation for RAM requirements and also I was
checking to ignite documentation on disk space required for WAL + WAL
archive.
here in this link
https://apacheignite.readme.io/d
Shivakumar,
Such allocation doesn’t allow full memory utilization, so it’s possible, that
nodes will crash because of out of memory errors.
So, it’s better to follow the given recommendation.
If you want us to investigate reasons of the failures, please provide logs and
configuration of the fai
Hi all,
we are testing field use case before deploying in the field and we want to
know whether below resource limits are suitable in production.
There are 3 nodes (3 pods on kubernetes) running. Each having below
configuration
DefaultDataRegion: 60GB
