This message:
Blocked system-critical thread has been detected. This can lead to
cluster-wide undefined behaviour [threadName=data-streamer-stripe-0,
blockedFor=34s]
is being printed in case if you're loading data to Ignite much faster than
it can write to the disk. The disk is a bottleneck here,
Hi all,
Can some one help me here. I still facing the serious performance issue.
Regards,
Favas
From: Muhammed Favas
Sent: Tuesday, September 24, 2019 2:15 PM
To: user@ignite.apache.org
Subject: RE: Ignite bulk data load issue
Thanks Igor for the suggestions.
But, In the log JVM pause is not
each node
>
>
>
>
>
> *Regards,*
>
> *Favas *
>
>
>
> *From:* Evgenii Zhuravlev
> *Sent:* Tuesday, September 24, 2019 12:44 PM
> *To:* user@ignite.apache.org
> *Subject:* Re: Ignite bulk data load issue
>
>
>
> Hi,
>
>
>
> Looks
Thanks Evgenii,
My cluster is AWS EC2 and below is the disk specification on each node
[cid:image001.png@01D572E3.AEEABE20]
Regards,
Favas
From: Evgenii Zhuravlev
Sent: Tuesday, September 24, 2019 12:44 PM
To: user@ignite.apache.org
Subject: Re: Ignite bulk data load issue
Hi,
Looks like
@ignite.apache.org
Subject: Re: Ignite bulk data load issue
Hi,
According to the logs, I see a lot of "Possible too long JVM pause" messages,
seems like you have a problem with GC activity. You should check GC logs and
try to tune GC following this manual:
https://apacheignite.readme.i
Hi,
Looks like you can have really slow disks. What kind of disk do you have
there? I see throttling in logs, Because the write operation is really
slow.
Evgenii
пн, 23 сент. 2019 г. в 13:07, Muhammed Favas <
favas.muham...@expeedsoftware.com>:
> Hi,
>
>
>
> I need help to figure out the issues
Hi,
According to the logs, I see a lot of "Possible too long JVM pause"
messages, seems like you have a problem with GC activity. You should check
GC logs and try to tune GC following this manual:
https://apacheignite.readme.io/docs/jvm-and-system-tuning
Also, it's suggested to disable WAL during
