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 23:17:00 GMT


Prasanth Jayachandran commented on HIVE-17508:

For some reason I cannot post some comments in RB. Posting it here

bq. Hive object is not threadsafe, passing it to runnable may not be valid. It should be obtained
on the thread that's going to use it.
Hive object is not passed to validator thread here. MetastoreGlobalTriggersFetcher gets executed
in the same thread fo TezSessionPoolManager. After fetching the triggers it will be passed
to validator thread.

> 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