You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Prasanth Jayachandran (JIRA)" <ji...@apache.org> on 2017/09/13 23:32:00 UTC

[jira] [Commented] (HIVE-17508) Implement pool rules and triggers based on counters

    [ https://issues.apache.org/jira/browse/HIVE-17508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165464#comment-16165464 ] 

Prasanth Jayachandran commented on HIVE-17508:
----------------------------------------------

[~sershe] Initial patch up for review. This currently is not hooked up with metastore rules yet (driven by configs now).
Also for elapsed time, we can map the rule to hive.query.timeout.seconds which HS2 already handles. Will add qtests after metastore integration. 


> 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.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)