-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-19567. S3A: error stack traces printed on analytics stream factory close #7701
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-19567. S3A: error stack traces printed on analytics stream factory close #7701
Conversation
…tory close catch all exception raised in stream close; log at debug
|
💔 -1 overall
This message was automatically generated. |
ahmarsuhail
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.
+1, LGTM.
out of curiosity, do you remember what the exception was?
|
@ahmarsuhail stack is in the JIRA, just submission of some asyc work failing. this is a much better failure than in the output stream case, which blocks...just that's an existing bug I only just noticed when manually stopping uploads (todo: add to the qualification) Note that this is in the SDK...it's not checking that the executor is open before presenting an explanation which is completely wrong. Will leave that for you to report. |
…tory close (#7701) Contributed by Steve Loughran
…tory close (#7701) Contributed by Steve Loughran
HADOOP-19567.
catch all exception raised in stream close; log at debug
How was this patch tested?
Surfaced during a cloudstore bandwidth test; manual testing can check.
Hard to write an ITest as it probably depends on the stream state at the time...will have to explore.
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?