You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/06/05 00:31:00 UTC

[jira] [Work logged] (HIVE-23596) LLAP: Encode initial guaranteed task information in containerId

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

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

                Author: ASF GitHub Bot
            Created on: 05/Jun/20 00:30
            Start Date: 05/Jun/20 00:30
    Worklog Time Spent: 10m 
      Work Description: mustafaiman closed pull request #1053:
URL: https://github.com/apache/hive/pull/1053


   


----------------------------------------------------------------
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:
users@infra.apache.org


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

    Worklog Id:     (was: 441608)
    Time Spent: 20m  (was: 10m)

> LLAP: Encode initial guaranteed task information in containerId
> ---------------------------------------------------------------
>
>                 Key: HIVE-23596
>                 URL: https://issues.apache.org/jira/browse/HIVE-23596
>             Project: Hive
>          Issue Type: Improvement
>          Components: llap
>            Reporter: Mustafa Iman
>            Assignee: Mustafa Iman
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> We should avoid calling LlapTaskScheduler to get initial isguaranteed flag for all the tasks. It causes arbitrary delays in sending tasks out. Since communicator is a single thread, any blocking there delays all the tasks.
> There are [https://jira.apache.org/jira/browse/TEZ-4192] and [https://jira.apache.org/jira/browse/HIVE-23589] for a proper solution to this. However, that requires a Tez release which seems far right now. We can replace the current hack with another hack that does not require locking.



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