[
https://issues.apache.org/jira/browse/HIVE-17508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16181825#comment-16181825
]
Sergey Shelukhin commented on HIVE-17508:
-----------------------------------------
Lots of comments. My main concern is that there should be one place that
validates the rules, it should not be diffuse everywhere in the code on
different threads and structure with multiple copies of the rules. It'd be
easier to reason about, and also require much less potential sync.
> Implement pool rules and triggers based on counters
> ---------------------------------------------------
>
> Key: HIVE-17508
> URL: https://issues.apache.org/jira/browse/HIVE-17508
> Project: Hive
> Issue Type: Sub-task
> Affects Versions: 3.0.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-17508.1.patch, HIVE-17508.2.patch,
> HIVE-17508.3.patch, HIVE-17508.3.patch, HIVE-17508.WIP.2.patch,
> HIVE-17508.WIP.patch
>
>
> Workload management can defined Rules that are bound to a resource plan. Each
> rule can have a trigger expression and an action associated with it. Trigger
> expressions are evaluated at runtime after configurable check interval, based
> on which actions like killing a query, moving a query to different pool etc.
> will get invoked. Simple rule could be something like
> {code}
> CREATE RULE slow_query IN resource_plan_name
> WHEN execution_time_ms > 10000
> MOVE TO slow_queue
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
