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 V (JIRA)" <ji...@apache.org> on 2019/04/24 17:23:00 UTC

[jira] [Updated] (HIVE-21646) Tez: Prevent TezTasks from escaping thread logging context

     [ https://issues.apache.org/jira/browse/HIVE-21646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gopal V updated HIVE-21646:
---------------------------
    Description: 
If hive.exec.parallel is set to true to parallelize MoveTasks or StatsTasks, the Tez task does not benefit from a new thread and will lose all the thread context of the current query.

Multiple threads even if they are spawned, will lock on SyncDagClient & make progress sequentially.

  was:If hive.exec.parallel is set to true to parallelize MoveTasks or StatsTasks, the Tez task does not benefit from a new thread and will lose all the thread context of the current query.


> Tez: Prevent TezTasks from escaping thread logging context
> ----------------------------------------------------------
>
>                 Key: HIVE-21646
>                 URL: https://issues.apache.org/jira/browse/HIVE-21646
>             Project: Hive
>          Issue Type: Bug
>          Components: Tez
>            Reporter: Gopal V
>            Assignee: Gopal V
>            Priority: Major
>
> If hive.exec.parallel is set to true to parallelize MoveTasks or StatsTasks, the Tez task does not benefit from a new thread and will lose all the thread context of the current query.
> Multiple threads even if they are spawned, will lock on SyncDagClient & make progress sequentially.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)