You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Harish Jaiprakash (JIRA)" <ji...@apache.org> on 2017/04/12 02:37:41 UTC
[jira] [Updated] (TEZ-1187) Share Thread pools between different
tasks
[ https://issues.apache.org/jira/browse/TEZ-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harish Jaiprakash updated TEZ-1187:
-----------------------------------
Attachment: TEZ-1187.06.patch
* Removed all usage of TezSharedExecutor, only exposing them through the contexts.
* Accepting a format and using thread id to generate unique thread name.
* Introduced configuration for min and max, but that required Configuration object. Which means its no longer a singleton and sharing is gone. Should I just introduce static method to initialize a singleton? Ideal way would be to pass down from the main method/class. In this case it would be TezChild.
> Share Thread pools between different tasks
> ------------------------------------------
>
> Key: TEZ-1187
> URL: https://issues.apache.org/jira/browse/TEZ-1187
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Harish Jaiprakash
> Attachments: TEZ-1187.02.patch, TEZ-1187.03.patch, TEZ-1187.04.patch, TEZ-1187.05.patch, TEZ-1187.06.patch, TEZ-1187.WIP.01.patch
>
>
> Thread pools are used all over for fetchers, sort etc. When running a single task - this is already a problem, and gets worse when running multiple tasks.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)