Hi, You have to also fetch values to do a "compare-and-delete". Before deleting each entry you check if it has been concurrently modified. If it was then it's possible that the entry doesn't match your WHERE anymore. So yes, for now deleting a large number of entries is heap-intensive.
It should improve when https://issues.apache.org/jira/browse/IGNITE-9182?jql=text%20~%20%22delete%20lazy%22%20and%20project%20%3D%20ignite is fixed. When it is done, you'll be able to set lazy=true for a DELETE and avoid the OOM. For now though I suggest to change the query in a way that it returns less entries, or use key-value API for deletions. Stan -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/