-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
HADOOP-16769 LocalDirAllocator to provide diagnostics when file creat… #1892
base: trunk
Are you sure you want to change the base?
Conversation
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.
looking good, the main thing it needs is that caught exception to be propagated to be the inner cause of the new exception raised. That way complicated failures don't lose their stack traces in the logs we get to see
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/LocalDirAllocator.java
Show resolved
Hide resolved
if (errorText != null) { | ||
newErrorText = newErrorText + " due to " + errorText; | ||
} | ||
throw new DiskErrorException(newErrorText); |
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.
if any exception had been caught and stored in L484, use it in the constructor/setCause here. Stack traces are too important to lose.
String dir0 = buildBufferDir(ROOT, 0); | ||
String dir1 = buildBufferDir(ROOT, 1); | ||
conf.set(CONTEXT, dir0 + "," + dir1); | ||
LambdaTestUtils.intercept(DiskErrorException.class, "as the max capacity" + |
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.
minor nit, move the "as the max" capacity string onto a line on its own' merge it back to a single string,
Thank you for the comments. For some reason I am not getting any email notifications about these git PR review comments. I just manually verified and found I missed to address these. I have addressed the comments and updated the PR. Can you please help me confirm the changes are expected? |
💔 -1 overall
This message was automatically generated. |
Sorry, I'd completely missed this too. @ramesh0201 -can you do a rebase and force push? I'd like to see what the checkstyle warnings were. Other than the checkstyle issues, the patch LGTM & is almost ready to go in |
Thanks @ramesh0201 for the PR. Wanted to check if you are still working on it or I can take it forward. |
@ashutoshcipher Please feel free to take it forward |
No description provided.