[
https://issues.apache.org/jira/browse/HIVE-24914?focusedWorklogId=570635&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-570635
]
ASF GitHub Bot logged work on HIVE-24914:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Mar/21 16:51
Start Date: 23/Mar/21 16:51
Worklog Time Spent: 10m
Work Description: pgaref opened a new pull request #2108:
URL: https://github.com/apache/hive/pull/2108
### What changes were proposed in this pull request?
schedulePendingTasks on the LlapTaskScheduler currently goes through all the
pending tasks and tries to allocate them based on their Priority – if a
priority can not be scheduled completely, we bail out as lower priorities would
not be able to get allocations either.
Only walk through the nodes with capacity (if any) ,and not all available
hosts, for scheduling these tasks based on their priority and locality
preferences.
### Why are the changes needed?
Scheduling perf
### Does this PR introduce _any_ user-facing change?
No
### How was this patch tested?
TestLlapTaskSchedulingService
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 570635)
Remaining Estimate: 0h
Time Spent: 10m
> Improve scheduling by only traversing hosts with capacity
> ---------------------------------------------------------
>
> Key: HIVE-24914
> URL: https://issues.apache.org/jira/browse/HIVE-24914
> Project: Hive
> Issue Type: Sub-task
> Reporter: Panagiotis Garefalakis
> Assignee: Panagiotis Garefalakis
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *schedulePendingTasks* on the LlapTaskScheduler currently goes through all
> the pending tasks and tries to allocate them based on their Priority -- if a
> priority can not be scheduled completely, we bail out as lower priorities
> would not be able to get allocations either.
> An optimization here could be to only walk through the nodes with capacity
> (if any) ,and not all available hosts, for scheduling these tasks based on
> their priority and locality preferences.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
