Re: JVM tuning parameters

[Andrey Gura <ag...@apache.org>]

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 problem analysis.

Also more detailed case description is required (it's just creation of
400 tables or some data also adding to the tables).

And finally... 1 core - is too hard restriction from my point of view.

On Sat, Mar 30, 2019 at 9:56 AM Denis Magda <dm...@gridgain.com> wrote:
>
> 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 Thu, Mar 28, 2019 at 6:58 AM ashfaq <as...@gmail.com> wrote:
>>
>> 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 this time it failed
>> at 300 tables.
>>
>> We would like to know how can we arrive at jvm heap size . Also we want to
>> know how do we configure such that the pods are not restarted and the
>> cluster is stable.
>>
>> Below are the current values that we have used.
>>
>> cpu - 1core
>> xms - 1GB
>> xmx - 2GB
>> RAM - 3GB
>>
>> Below is the error log:
>>
>> "Critical system error detected. Will be handled accordingly to configured
>> handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
>> super=AbstractFailureHandler [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]],
>> failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
>> o.a.i.IgniteException: GridWorker [name=db-checkpoint-thread,
>> igniteInstanceName=null, finished=false, heartbeatTs=1553771825864]]] class
>> org.apache.ignite.IgniteException: GridWorker [name=db-checkpoint-thread,
>> igniteInstanceName=null, finished=false, heartbeatTs=1553771825864]
>>         at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1831)
>>         at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1826)
>>         at
>> org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:233)
>>         at
>> org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:297)
>>         at
>> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.lambda$new$0(ServerImpl.java:2663)
>>         at
>> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7181)
>>         at
>> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2700)
>>         at
>> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
>>         at
>> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7119)
>>         at
>> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/