[IMPALA-8792] User Defined Admission Rules

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Backend
• Labels: admission-control resource-management
• Epic Color: ghx-label-1
• Assignee: Unassigned
• Reporter: Quanlong Huang
• Created: 25/Jul/19 05:19
• Updated: 23/Dec/20 00:28

Description

Impala cluster may be shared by many products. Admin may want to ban some queries as a work around for some bugs or known limitations, to avoid problematic queries impact the whole cluster.

The rules can base on user names, query text, AST after parsing, or the plan after analysis. It'd be better if admin can add/delete/modify rules without restarting the coordinators.

Example rules:

• Ban all queries submitted from user idiot_product_name
• Ban all queries containing text "application-name=xxx" (usually added as hint, used to recognize a product)
• Ban all queries with text length larger than a threshold
• Ban all queries that joins more than 20 tables (require AST)
• Ban all queries that joins two specify fact tables (require AST)
• Ban all queries using specify wrong join path (require AST)
• Ban all queries that contain too complex expressions, e.g. #nodes in the expression tree exceeding a threshold (require AST)