You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Gopal Vijayaraghavan (Jira)" <ji...@apache.org> on 2020/06/04 17:17:00 UTC
[jira] [Updated] (HIVE-23596) LLAP: Encode initial guaranteed task
information in containerId
[ https://issues.apache.org/jira/browse/HIVE-23596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gopal Vijayaraghavan updated HIVE-23596:
----------------------------------------
Summary: LLAP: Encode initial guaranteed task information in containerId (was: LLAP: Encode guaranteed task information in containerId)
> 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
> Reporter: Mustafa Iman
> Assignee: Mustafa Iman
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> 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)