-
Notifications
You must be signed in to change notification settings - Fork 9.2k
[YARN-11353] : Change debug logs in FSDownload.java to info logs for better escalations debugging #5061
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…better escalations debugging
|
💔 -1 overall
This message was automatically generated. |
hotcodemacha
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Sahu3426 for your contribution. Can you fix the Yetus errors?
|
💔 -1 overall
This message was automatically generated. |
|
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. |
Description of PR
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.