Those options are not available in Ignite. There are solutions built on top of Ignite that support SQL quotas.
> On 27 May 2021, at 06:17, Kamlesh Joshi <kamlesh.jo...@ril.com> wrote: > > Hi Craig, > > Yes, query is returning many records. But, we can not control who executes > which type of command. However, cluster should be stable enough to handle > such queries. > > Somewhere I have seen below few properties for the same, are those not > available in Ignite open source? > sqlQueryMemoryQuota > sqlOffloadingEnabled > sqlGlobalMemoryQuota > > > Thanks and Regards, > Kamlesh Joshi > > From: Craig Gresbrink <cgresbr...@24hourfit.com > <mailto:cgresbr...@24hourfit.com>> > Sent: 26 May 2021 21:17 > To: user@ignite.apache.org <mailto:user@ignite.apache.org> > Subject: [External]RE: Ignite nodes crash after firing heavy SQL query > > The e-mail below is from an external source. Please do not open attachments > or click links from an unknown or suspicious origin. > > > > 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 <mailto:kamlesh.jo...@ril.com>> > Sent: Wednesday, May 26, 2021 5:54 AM > To: user@ignite.apache.org <mailto: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’. > Is there any way available to kill such queries ? > Any way to set SQL query timeout at cluster level? > Any parameters that we should be tweaking to avoid this? > > Thanks and Regards, > Kamlesh Joshi >
