[ 
https://issues.apache.org/jira/browse/HIVE-24116?focusedWorklogId=478451&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-478451
 ]

ASF GitHub Bot logged work on HIVE-24116:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Sep/20 10:13
            Start Date: 03/Sep/20 10:13
    Worklog Time Spent: 10m 
      Work Description: rbalamohan opened a new pull request #1466:
URL: https://github.com/apache/hive/pull/1466


   https://issues.apache.org/jira/browse/HIVE-24116
   
   Remote storage reads can be avoided, if an opportunity is provided for these 
preempted to get better locality in next iteration.


----------------------------------------------------------------
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:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 478451)
    Remaining Estimate: 0h
            Time Spent: 10m

> LLAP: Provide an opportunity for preempted tasks to get better locality in 
> next iteration
> -----------------------------------------------------------------------------------------
>
>                 Key: HIVE-24116
>                 URL: https://issues.apache.org/jira/browse/HIVE-24116
>             Project: Hive
>          Issue Type: Improvement
>          Components: llap
>            Reporter: Rajesh Balamohan
>            Assignee: Rajesh Balamohan
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In certain DAGs, tasks get preempted as higher priority tasks need to be 
> executed. These preempted tasks are scheduled to run later, but they end up 
> missing locality information. Ref: HIVE-24061
> Remote storage reads can be avoided, if an opportunity is provided for these 
> preempted to get better locality in next iteration.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to