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

Shilun Fan resolved YARN-11277.
-------------------------------
       Fix Version/s: 3.4.0
        Hadoop Flags: Reviewed
    Target Version/s: 3.4.0
          Resolution: Fixed

> trigger deletion of log-dir by size for NonAggregatingLogHandler
> ----------------------------------------------------------------
>
>                 Key: YARN-11277
>                 URL: https://issues.apache.org/jira/browse/YARN-11277
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 3.4.0
>            Reporter: Xianming Lei
>            Assignee: Xianming Lei
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>
> In our yarn cluster, the log files of some containers are too large, which 
> causes the NodeManager to frequently switch to the unhealthy state. For logs 
> that are too large, we can consider deleting them directly without delaying 
> yarn.nodemanager.log.retain-seconds.
> Cluster environment:
>  # 8k nodes+
>  # 50w+ apps  / day
> Configuration:
>  # yarn.nodemanager.log.retain-seconds=3days
>  # yarn.log-aggregation-enable=false
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

Reply via email to