You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Xiping Zhang (Jira)" <ji...@apache.org> on 2021/05/21 06:03:00 UTC
[jira] [Comment Edited] (YARN-10781) The Thread of the NM aggregate
log is exhausted and no other Application can aggregate the log
[ https://issues.apache.org/jira/browse/YARN-10781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348991#comment-17348991 ]
Xiping Zhang edited comment on YARN-10781 at 5/21/21, 6:02 AM:
---------------------------------------------------------------
When NM accepts an Application , it initializes an ApplogAggregatorImpl internally and drops it into a thread pool with a default size of 100.Each thread is responsible for reporting the log of an Application until the Application Finish or aborted.
A maximum of 100 running applications can be processed simultaneously.Due to SparkStreaming's dynamic resource mechanism, it is possible that such threads on NM cannot exit even though there is no Container running on it.Increasing the number of core threads in the thread pool is possible, but this is not a good solution, as the number of sparkStreaming appliacations increases, resulting in more threads being occupied. U can correct me if there is any problem with my understanding
was (Author: zhangxiping):
When NM accepts an Application container, it initializes an ApplogAggregatorImpl internally and drops it into a thread pool with a default size of 100.Each thread is responsible for reporting the log of an Application until the Application Finish or aborted.
A maximum of 100 running applications can be processed simultaneously.Due to SparkStreaming's dynamic resource mechanism, it is possible that such threads on NM cannot exit even though there is no Container running on it.Increasing the number of core threads in the thread pool is possible, but this is not a good solution, as the number of sparkStreaming appliacations increases, resulting in more threads being occupied. U can correct me if there is any problem with my understanding
> The Thread of the NM aggregate log is exhausted and no other Application can aggregate the log
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-10781
> URL: https://issues.apache.org/jira/browse/YARN-10781
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Affects Versions: 2.9.2, 3.3.0
> Reporter: Xiping Zhang
> Priority: Major
>
> We observed more than 100 applications running on one NM.Most of these applications are SparkStreaming tasks, but these applications do not have running Containers.When the offline application running on it finishes, the log cannot be reported to HDFS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org