[
https://issues.apache.org/jira/browse/HIVE-10406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stamatis Zampetakis updated HIVE-10406:
---------------------------------------
I cleared the fixVersion field since this ticket is still open. Please review
this ticket and if the fix is already committed to a specific version please
set the version accordingly and mark the ticket as RESOLVED.
According to the [JIRA
guidelines|https://cwiki.apache.org/confluence/display/Hive/HowToContribute]
the fixVersion should be set only when the issue is resolved/closed.
> 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
> Components: llap
> Reporter: Siddharth Seth
> Priority: Major
> 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
(v8.20.10#820010)
