hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <>
Subject [jira] [Commented] (HIVE-17508) Implement global execution triggers based on counters
Date Fri, 13 Oct 2017 21:29:00 GMT


Prasanth Jayachandran commented on HIVE-17508:

There is a TODO which says per pool validation runnable has to be implemented. The validator
runnable is get all triggers and apply which only works for TezSessionPoolManager. For WorkloadManager,
i will add it in a followup that will change the runnable to per pool validator?
Will address your other concerns in the next patch.

> Implement global execution triggers based on counters
> -----------------------------------------------------
>                 Key: HIVE-17508
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>    Affects Versions: 3.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>         Attachments: HIVE-17508.1.patch, HIVE-17508.10.patch, HIVE-17508.11.patch, HIVE-17508.2.patch,
HIVE-17508.3.patch, HIVE-17508.3.patch, HIVE-17508.4.patch, HIVE-17508.5.patch, HIVE-17508.6.patch,
HIVE-17508.7.patch, HIVE-17508.8.patch, HIVE-17508.9.patch, HIVE-17508.WIP.2.patch, HIVE-17508.WIP.patch
> Workload management can defined Triggers that are bound to a resource plan. Each trigger
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 execution trigger could be
something like
> {code}
> CREATE TRIGGER slow_query IN global
> WHEN execution_time_ms > 10000
> MOVE TO slow_queue
> {code}

This message was sent by Atlassian JIRA

View raw message