Hello!
SQL query intermediate results are held on heap. If you run out of heap,
your application will crash.
There are three ways to mitigate it:
1) Use lazy=false parameter of Ignite JDBC or native SQL API. This will try
to limit amount of results held on heap.
2) Rewrite your queries.
3) Wait f
You ran out of Java heap-space, It’s more efficient to use the IgniteCache
class for these kinds of operation. You can use IgniteCache#clear() to remove
all records from a cache, for example.
> On 30 Sep 2020, at 12:05, ashishb888 wrote:
>
> I am performing a delete query on a cache which has
I am performing a delete query on a cache which has large data. When query
start application CPU utilization goes around 2000, and application crashes
with below error message,
2020-09-30 11:21:31.682 ERROR 128023 ---
[grid-nio-worker-tcp-comm-5-#68%TcpCommunicationSpi%] ROOT
