Hello, Igniters.
We see some strange things happening: execution time is growing if we
execute same query concurrently in multiple threads.
And it doesn't matter if we query existing or not existing cache!
Very simple reproducer and it's execution results are attached.
We test it on prod node and
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
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
Thank you!
Actually I do not use persistence, and all the data stored in the RAM.
Do we have similar things for the data stored in the RAM?
BR,
Ashish
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hello!
Why would you want to do this?
Try removing part-NNN.bin from your persistence to achieve this. Be sure to
check in on testing first.
Regards,
--
Ilya Kasnacheev
ср, 30 сент. 2020 г. в 13:47, ashishb888 :
> Is is possible to purge a Ignite partition? If yes, how can we achieve? and
>
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
Is is possible to purge a Ignite partition? If yes, how can we achieve? and
will it advisable to do so?
BR,
Ashish
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
