[ 
https://issues.apache.org/jira/browse/YARN-11402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18033724#comment-18033724
 ] 

ASF GitHub Bot commented on YARN-11402:
---------------------------------------

github-actions[bot] commented on PR #5247:
URL: https://github.com/apache/hadoop/pull/5247#issuecomment-3459165566

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> Meaningless logs are frequently printed during ResourceManager startup and 
> recover container.
> ---------------------------------------------------------------------------------------------
>
>                 Key: YARN-11402
>                 URL: https://issues.apache.org/jira/browse/YARN-11402
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Daniel Ma
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: screenshot-1.png, screenshot-2.png
>
>
> Tens of thousands of meaningless logs are frequently printed during 
> ResourceManager startup and recover container.
> As we know, ResourceManager will always keep 10k application information by 
> default. In our very big scale cluster, it is very usual that resourcemanager 
> try to recover the containers which already finished and does not exist in 
> ResourceManager but still reported by nodemanager.
> Under this case, below logs will be frequently printed,  more importantly, 
> this log is meaningless, in real production setups, the maintainers actually 
> more care about which containers are properly recovered or killed not the 
> ones are skipped.
> The related code are as follows,
>  !screenshot-1.png! 
> So we move the log into function killOrphanContainerOnNode().
>  !screenshot-2.png! 
> Only the containers to be killed need to be loged  which is vital for trouble 
> shooting to distinguish whether the containers are kill by hadoop inner 
> mechanism or by users themselves.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to