[IMPALA-8418] Restrict user from setting resource limits to high values at session level

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Backend
• Target Version: Product Backlog
• Epic Color: ghx-label-1
• Assignee: Unassigned
• Reporter: Bikramjeet Vig
• Created: 15/Apr/19 21:47
• Updated: 23/Dec/20 01:26

Description

A user/client can set a very high value for any of the resource limits (eg. MEM_LIMIT, THREAD_RESERVATION_AGGREGATE_LIMIT, etc) which can potentially make the cluster unstable and affect other queries.
Possible solution to this problem can include restricting a user to override resource limits. However any solution would need to be scope, taking into account things like:

• capping limits at the service level and/or the resource pool level
• Effects of dynamically changing resource pools configs
• Some implementation of safety valves - to cover cases like if we want to run a query with a value outside the range, e.g. some special query that needs tuning
• Authorisation - who is allowed to change and/or override limit

Some form of this has been implemented in IMPALA-7349 where you can set min/max limits on mem_limit and using the clamp-mem-limit-query-option config, you can toggle whether these limits can be overridden by the user

Issue Links

• relates to: IMPALA-7349 Automatically choose mem_limit based on estimate, clamped to range