Hi,
SQL query may be potential cause of the OOM.
Please check that:
1. Simple scan+filter queries (e.g. SELECT * FROM WHERE )
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
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
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/
HI,
We are using Apache Ignite 2.7.0 binary and servers are using Linux OS &
app servers are using Windows OS.We are using Apache Ignite .Net APIs.
Recently we have noticed that our application (Client Node) is stopping
with OOM error. App server has 32 GB RAM & we are specifying JVM Heap = 8
