Hi,
SQL query may be potential cause of the OOM.
Please check that:
1. Simple scan+filter queries (e.g. SELECT * FROM <src> WHERE <cond>)
that may produce big results run in lazy mode (SqlFieldsQuery#setLazy);
2. Queries that requires not indexing sort or group aggregates don't
produce big result set (lazy mode isn't applied).
On 06.11.2020 17:07, Ravi Makwana wrote:
Hi,
*1) What load profile do you have? *
Ans: We have 2 clusters, each having 2 nodes, one cluster is having
approx 15 GB data (Replication) & second cluster is having approx 5 GB
data (Partitioned) with eviction policy.
*
*
*2) Do you use SQL queries?*
Ans: Yes, We are using.
*
*
*3) Is it possible to share your client node configuration?*
Ans: Yes, I have attached below.
Thanks,
On Fri, 6 Nov 2020 at 18:50, Vladimir Pligin <[email protected]
<mailto:[email protected]>> wrote:
What load profile do you have? Do you use SQL queries? Is it
possible to
share your client node configuration?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
<http://apache-ignite-users.70518.x6.nabble.com/>
--
Taras Ledkov
Mail-To: [email protected]
