Ability to limit HANA resource usage for end users

[Former Member]

A question regarding the possibities within HANA to limit the resource usage for (specific) end users.

A HANA platform (single node) is set-up in such a way that end users are allowed to create queries (via BI 4.x). However, several times already there was the situation where an end user created a query which consumed all resources of the HANA platform (for now, not focussing on training these end users, or making sure they create a decent query, etc). This resource consumption already lead to the unavailability of the platform, and even a direct restart of the HANA platform (unexpectedly initiated by HANA itself).

So, is it possible to limit the resource consumption for users (like preventing expensive statements)? Is there a particular setting in HANA to do this? Or is it just a matter of ‘educating’ end users?

Thanks!

Stefan

[lbreddemann · Accepted solution]

Hi Stefan,

currently (rev. 70) there is no effective way to limit the amount of resources that can be used by any given SQL query.

Development in currently implementing such features (e.g. the statement_memory_limit-parameter, attention the unit is GB!!) but is not yet done with it.

So for now, all you can do is either educate the users or adapt your models accordingly.

In any case, out of memory situations shouldn't bring down the whole instance, but trigger an indexserver restart in the worst case.

You should open a support incident for this to find the exact cause for this.

Sorry to not have a more satisfying answer for now.

- Lars

[Former Member · Accepted solution]

Lars,

Thanks for this answer! It's helpfull in the sense that we know we didn't miss a setting/parameter.

Grz,

Stefan

[Former Member]

Rev 72

statement_memory_limit  parameter founded in INI files.

Is it works?

[justin_molenaur2]

From the information I head from , and found in the performance guide on page 22, this is activated in SPS08.

This is a good step to avoid taking the box down too frequently by runaway queries.

http://help.sap.com/hana/SAP_HANA_Troubleshooting_and_Performance_Analysis_Guide_en.pdf

Regards,

Justin