You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tez.apache.org by "Panagiotis Garefalakis (Jira)" <ji...@apache.org> on 2020/07/30 22:05:00 UTC
[jira] [Created] (TEZ-4213) Bound appContext executor capacity
using a configurable property
Panagiotis Garefalakis created TEZ-4213:
-------------------------------------------
Summary: Bound appContext executor capacity using a configurable property
Key: TEZ-4213
URL: https://issues.apache.org/jira/browse/TEZ-4213
Project: Apache Tez
Issue Type: Bug
Reporter: Panagiotis Garefalakis
Assignee: Panagiotis Garefalakis
After TEZ-4170 was merged, appContext executor pool is also used by the RootInputInitializerManager to speed up SplitGeneration.
However, this executor pool currently has not capacity limit https://github.com/apache/tez/blob/master/tez-dag/src/main/java/org/apache/tez/dag/app/DAGAppMaster.java#L624
When generating splits for larger inputs (thousands or more) this could result in
{color:red}java.lang.OutOfMemoryError: unable to create new native thread{color}
(reproducible with a test case)
I propose to limit the capacity of this pool to a configurable value that can be for example the number of physical cores by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)