-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-18455. s3a prefetching Executor should be closed #4879
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
… submitting work (ADDENDUM)
|
Tested against
|
|
@steveloughran @mehakmeet could you please review this addendum patch? |
|
💔 -1 overall
This message was automatically generated. |
|
@mukund-thakur could you please also review? |
|
💔 -1 overall
This message was automatically generated. |
mehakmeet
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.
LGTM pending yetus errors, Also I think it's better to create this as a separate Hadoop Jira ticket, just to keep track of the changes and explain what the changes are. We can always add the previous Hadoop Jira as the follow-up in the commit message.
mukund-thakur
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.
I have never seen reopening jira's in Hadoop unless it is a critical BUG and that too we always fix via a new JIRA.
I see the issue here is not shutting down the thread pool. Could you please create a new jira and update it this same PR. you can add "follow on <original_jira_id> " in the commit message.
...adoop-common/src/main/java/org/apache/hadoop/fs/impl/prefetch/ExecutorServiceFuturePool.java
Show resolved
Hide resolved
Nice @mehakmeet already commented the same above. |
|
@mehakmeet @mukund-thakur I will create a new follow-up Jira, thanks |
|
Updated the PR title with new Jira. |
This would be the case for other thread pools also that are shutdown as part of the filesystem close. |
mukund-thakur
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.
LGTM +1
I am wondering how can we ignore this yetus failure and let it run successfully for build and checkstyle.
I agree that spotbug is not an issue here. It is just a false alarm I guess. Will work with @steveloughran to merge this.
|
edit the spotbugs file to tell it to STFU |
|
💔 -1 overall
This message was automatically generated. |
mukund-thakur
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.
LGTM +1,
Yetus failure because of no new tests, so ignoring that.
|
that spotbugs change is too broad, now it will ignore all inconsistent uses in the class. Can you do a followup which restricts it only to those methods which have problems. otherwise i'll be reverting this... |
|
I tried applying to |
|
Moreover, we also have the same suppress rule applied to S3AInputStream as well: |
|
We can still suppress it at field level, if not at method level. Will create PR for HADOOP-18466 soon. |
|
@steveloughran @mukund-thakur @mehakmeet the spotbugs follow up PR is ready for review: #4926 |
follow-on patch to HADOOP-18186. Contributed by: Viraj Jasani
follow-on patch to HADOOP-18186. Contributed by: Viraj Jasani
follow-on patch to HADOOP-18186. Contributed by: Viraj Jasani
follow-on patch to HADOOP-18186. Contributed by: Viraj Jasani
follow-on patch to HADOOP-18186. Contributed by: Viraj Jasani
No description provided.