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

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

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

   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.




> Change debug logs in FSDownload.java to info logs for better escalations 
> debugging
> ----------------------------------------------------------------------------------
>
>                 Key: YARN-11353
>                 URL: https://issues.apache.org/jira/browse/YARN-11353
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager, yarn
>    Affects Versions: 3.4.0
>            Reporter: Sanjay Kumar Sahu
>            Assignee: Sanjay Kumar Sahu
>            Priority: Major
>              Labels: pull-request-available
>
> AM was stuck in Preparing Local resources step and it timed out and never 
> started the driver. This happened in one of the customer's cluster and got 
> resolved when this cluster got deleted and the customer started using another 
> cluster . The logs were not enough to look into the issue. Adding more info 
> logs will help to understand when did the download of the files start and 
> when did it end, or whether it actually reached that step like adding the 
> containerId here to know who is downloading.
>  



--
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