[
https://issues.apache.org/jira/browse/HIVE-23238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087376#comment-17087376
]
Gopal Vijayaraghavan commented on HIVE-23238:
---------------------------------------------
bq. I believe this kind of decisions could also be taken into account from the
AM side
Unfortunately, there's no mechanism for this, as of yet - the LLAP AMs don't
talk to each other or to any central resource negotiator (i.e 600 tasks could
all be Guaranteed in a 1000 node cluster, but have the same node for locality).
The collision in locality is emergent behaviour & also sensitive for the order
of submission for preemption.
> FIX PreemptionQueueComparator edge cases
> ----------------------------------------
>
> Key: HIVE-23238
> URL: https://issues.apache.org/jira/browse/HIVE-23238
> Project: Hive
> Issue Type: Improvement
> Reporter: Panagiotis Garefalakis
> Assignee: Panagiotis Garefalakis
> Priority: Major
> Labels: pull-request-available
> Fix For: llap
>
> Attachments: HIVE-23238.01.patch, HIVE-23238.02.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Properly handle preemption comparator edge cases where tasks are same type
> and have the same number or upstream tasks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
