Decreasing perNodeBufferSize and setting perNodeParallelOperations to
server_cpu_cores * 2 may help if GC load is high.
Yes, it can be AWS related issue, either connectivity or disk I/O. There
were reports about cluster segmentation due to network problems on AWS.
Please share full server/client logs and full thread dumps taken at the
moment of freeze. It will certainly help in analysis.
Best Regards,
Ivan Rakov
On 20.02.2018 22:24, lawrencefinn wrote:
Should I decrease these? One other thing to note is im monitoring GC and the
GC times do not correlate with these issues (GC times are pretty low
anyway). I honestly think that persisting to disk somehow causes things to
freeze up. Could it be an AWS related issue? Im using EBS IO1 with 20,000
IOPS, one driver for persistence and one for wal.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
