ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ilya Kasnacheev <ilya.kasnach...@gmail.com>
Subject Re: Ignite node stops on read/insert/update operations from ycsb
Date Thu, 06 Dec 2018 14:47:25 GMT

Maybe you queue too much data on one side so that it cannot be transferred
to destination in time. If you have connection pair, there's less
congestion and maybe you are able to free that data. You could try to fix
this by limiting queueing:

"Message queue limit is set to 0 which may lead to potential OOMEs when
running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to message
queues growth on sender and receiver sides."

This is by setting tcpCommunicationSpi.messageQueueLimit.

Ilya Kasnacheev

чт, 6 дек. 2018 г. в 10:19, summasumma <bytestreams@gmail.com>:

> Hi Ilya,
> The outofmemory error is coming after 5 seconds from the following 1st
> error: So i suspect the heap is increased only after initially hitting the
> following issue.
> "[19:07:36,283][SEVERE][grid-nio-worker-tcp-comm-3-#28][TcpCommunicationSpi]
> Failed to process selector key [ses=GridSelectorNioSessionImpl
> [worker=DirectNioClientWorker.... "
> Also one more update is if i enable connectionpair, this issue goes away
> with exactly same setup/parameters. So trying to find the connection.
> Thanks,
> ...summa
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

View raw message