Can you provide the query and the explain plan of the query (via Ignite Web Console)?
First step I would suggest is to seek to tune the query, maybe it needs an index, or the driving table needs to be changed, or maybe the query uses indexes correctly but many rows are returned from the driving table. From: Kamlesh Joshi <kamlesh.jo...@ril.com> Sent: Wednesday, May 26, 2021 5:54 AM To: user@ignite.apache.org Subject: Ignite nodes crash after firing heavy SQL query CAUTION: This email originated outside 24 Hour Fitness. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Igniters, We want to use Ignite (v2.7.6) mostly via SQL for operational activities (adding extra indexes to enable querying). While doing POC, observed that if any heavy query is fired, few nodes from the clusters are going down due to 'OOM Error'. 1. Is there any way available to kill such queries ? 2. Any way to set SQL query timeout at cluster level? 3. Any parameters that we should be tweaking to avoid this? Thanks and Regards, Kamlesh Joshi "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential and may be privileged. If you are not the intended recipient, you are hereby notified that any review, re-transmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."
