BTW, Taras has created the ticket
https://issues.apache.org/jira/browse/IGNITE-9379.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
I believe, you should file a ticket on this one.
Best Regards,
Igor
On Fri, Aug 24, 2018 at 5:57 PM dmitrievanthony
wrote:
> I've rebuilt Ignite from master and tried again, but the behaviour is the
> same. If the page is very big (compare with heap size) server node fails
> with OOM and the c
I've rebuilt Ignite from master and tried again, but the behaviour is the
same. If the page is very big (compare with heap size) server node fails
with OOM and the client hangs.
[14:54:06,273][SEVERE][client-connector-#101][ClientListenerProcessor]
Runtime error caught during grid runnable executi
Hi,
Unfortunatelly, scan query doesn't supports timeout at all, neither via
binary client not java API.
OOM can be caused by known bug [1]. Fix is already in master and will be
available in next release.
[1] https://issues.apache.org/jira/browse/IGNITE-8892
On Thu, Aug 23, 2018 at 11:37 PM dmitr
Is it a parameter of query? I see it in the list of OP_QUERY_SQL parameters,
but not in list of OP_QUERY_SCAN which I use
(https://apacheignite.readme.io/v2.6/docs/binary-client-protocol-sql-operations).
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Hi, do you have query timeout configured?
D.
On Thu, Aug 23, 2018 at 9:09 AM, dmitrievanthony
wrote:
> When I'm sending Scan Query request via Binary Client Protocol with very
> big
> page size I get OOM on the server node:
> java.lang.OutOfMemoryError: Java heap space at
> org.apache.ignit
