[
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.05.patch
* Reverted changes for framework and tests.
* Created interface to generate ExecutorService, currently we have only one
implementation and is no pluggable. LogicalIOProcessorRuntimeTask directly
interacts with TezSharedExecutor, but rest of the places we use the interface.
* Left thread name in the interface, we cannot use a pattern since Threads are
re-used and the count will not have much meaning for a given executor. But I
thought its useful to have a name to know which context its being used. We
cannot have a ThreadFactory for each executor service created, which will void
shared threads.
* Converted poller thread into daemon thread, it was causing test failures
after all the changes to the tests were reverted.
* Removed unnecessary implements ExecutorService.
> 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.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)
