[
https://issues.apache.org/jira/browse/HBASE-30155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18082143#comment-18082143
]
Hudson commented on HBASE-30155:
--------------------------------
Results for branch branch-3
[build #568 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/568/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/568/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/568/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
> MobFileCleanerChore does not shut down its internal executor on cleanup
> -----------------------------------------------------------------------
>
> Key: HBASE-30155
> URL: https://issues.apache.org/jira/browse/HBASE-30155
> Project: HBase
> Issue Type: Bug
> Components: mob
> Reporter: Xiao Liu
> Assignee: Xiao Liu
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.5.15, 2.6.6
>
>
> {\{MobFileCleanerChore}} creates its own \{{ThreadPoolExecutor}} for cleaning
> MOB files in parallel, but it does not override \{{ScheduledChore.cleanup()}}
> to shut down the executor.
> {\{HMaster.stopChores()}} calls \{{shutdownChore(mobFileCleanerChore)}},
> which eventually invokes \{{ScheduledChore.shutdown()}} and then
> \{{cleanup()}}. However, the default \{{ScheduledChore.cleanup()}}
> implementation is empty, so the \{{mobfile-cleaner-pool-*}} threads created
> by \{{MobFileCleanerChore}} are left running after the chore is shut down.
> The fix is to override \{{cleanup()}} in \{{MobFileCleanerChore}} and shut
> down the internal executor, for example by calling
> \{{executor.shutdownNow()}}. A unit test should verify that
> \{{MobFileCleanerChore.shutdown()}} shuts down the executor.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
