hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HIVE-10406) LLAP: Make use of additional information to determine run/preemption order
Date Mon, 20 Apr 2015 20:28:58 GMT
Siddharth Seth created HIVE-10406:
-------------------------------------

             Summary: LLAP: Make use of additional information to determine run/preemption
order
                 Key: HIVE-10406
                 URL: https://issues.apache.org/jira/browse/HIVE-10406
             Project: Hive
          Issue Type: Sub-task
            Reporter: Siddharth Seth
             Fix For: llap


The preemption will evolve as it's tested.
Had a discussion offline with [~hagleitn]. The initial policy will likely be the following.

Within a running DAG, the priority / topo order decides which fragment runs / is a candidate
for preemption.
Beyond this, the number of tasks in the current vertex + upstream vertices will be used as
a measure of the size of the query to determine which fragment gets to run, if there's multiple
fragments queued up. Fragments with a lower count will be preferred to push through what are
expected to be shorter running queries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message