[
https://issues.apache.org/jira/browse/HIVE-23210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084221#comment-17084221
]
Gopal Vijayaraghavan commented on HIVE-23210:
---------------------------------------------
bq. Are you suggesting to run single task jobs at higher priority compared to
rest of tasks in daemon.
No, this is specifically for the comparator which has 1 task vertices on both
sides, not that scenario.
The current problem is that the comparator returns 0 when comparing 1 task
vertices - which causes them to be scheduled at random rather than in the order
of the request time or by any other meaningful priority.
> Fix shortestjobcomparator when jobs submitted have 1 task their vertices
> ------------------------------------------------------------------------
>
> Key: HIVE-23210
> URL: https://issues.apache.org/jira/browse/HIVE-23210
> Project: Hive
> Issue Type: Improvement
> Reporter: Rajesh Balamohan
> Priority: Major
> Attachments: TestShortestJobFirstComparator.java
>
>
> In latency sensitive queries, lots of jobs can have vertices with 1 task.
> Currently shortestjobcomparator does not work correctly and returns tasks in
> random order.
> [https://github.com/apache/hive/blob/master/llap-server/src/java/org/apache/hadoop/hive/llap/daemon/impl/comparator/ShortestJobFirstComparator.java#L51]
> This causes delay in the job runtime. I will attach a simple test case
> shortly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
