-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-25692 Always try to close the WAL reader when we catch any exce… #3090
HBASE-25692 Always try to close the WAL reader when we catch any exce… #3090
Conversation
…ption There are code paths in which we throw non-IOExceptions when initializing a WAL reader. However, we only close the InputStream to the WAL filesystem when the exception is an IOException. Close it if it is open in all cases.
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
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.
Nice fix.
…ption (#3090) There are code paths in which we throw non-IOExceptions when initializing a WAL reader. However, we only close the InputStream to the WAL filesystem when the exception is an IOException. Close it if it is open in all cases. Co-authored-by: Josh Elser <jelser@cloudera.com> Signed-off-by: Andrew Purtell <apurtell@apache.org>
…ption (#3090) There are code paths in which we throw non-IOExceptions when initializing a WAL reader. However, we only close the InputStream to the WAL filesystem when the exception is an IOException. Close it if it is open in all cases. Co-authored-by: Josh Elser <jelser@cloudera.com> Signed-off-by: Andrew Purtell <apurtell@apache.org>
…ption (#3090) There are code paths in which we throw non-IOExceptions when initializing a WAL reader. However, we only close the InputStream to the WAL filesystem when the exception is an IOException. Close it if it is open in all cases. Co-authored-by: Josh Elser <jelser@cloudera.com> Signed-off-by: Andrew Purtell <apurtell@apache.org>
Thanks for merging this in, Stack. Had it on my list but other things kept bumping it off. I'll follow up checking 1.x in Jira. |
…ption (#3090) There are code paths in which we throw non-IOExceptions when initializing a WAL reader. However, we only close the InputStream to the WAL filesystem when the exception is an IOException. Close it if it is open in all cases. Co-authored-by: Josh Elser <jelser@cloudera.com> Signed-off-by: Andrew Purtell <apurtell@apache.org>
…ption (apache#3090) There are code paths in which we throw non-IOExceptions when initializing a WAL reader. However, we only close the InputStream to the WAL filesystem when the exception is an IOException. Close it if it is open in all cases. Co-authored-by: Josh Elser <jelser@cloudera.com> Signed-off-by: Andrew Purtell <apurtell@apache.org> (cherry picked from commit a227a4a) Change-Id: Id705661faa3f8eb3fcec59ddaef5fcb3f0138f87
…ption
There are code paths in which we throw non-IOExceptions when
initializing a WAL reader. However, we only close the InputStream to the
WAL filesystem when the exception is an IOException. Close it if it is
open in all cases.