[ 
https://issues.apache.org/jira/browse/HBASE-30209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18088801#comment-18088801
 ] 

Hudson commented on HBASE-30209:
--------------------------------

Results for branch branch-3
        [build #576 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/576/]: 
(/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/576/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/576/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


> MobFileCleanerChore is not registered for online configuration updates
> ----------------------------------------------------------------------
>
>                 Key: HBASE-30209
>                 URL: https://issues.apache.org/jira/browse/HBASE-30209
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, 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.16, 2.6.7
>
>
> {\{MobFileCleanerChore}} implements \{{ConfigurationObserver}}, but 
> \{{HMaster}} only creates and schedules the chore and does not register it 
> with \{{ConfigurationManager}}.
> Because of this, online configuration reloads triggered by \{{update_config}} 
> do not reach \{{MobFileCleanerChore}}. In practice, changes such as 
> \{{hbase.master.mob.cleaner.threads}} do not take effect until the master is 
> restarted.
> This patch registers \{{MobFileCleanerChore}} with \{{ConfigurationManager}} 
> during initialization, deregisters it during shutdown, and adds tests to 
> cover both the \{{HMaster}} wiring and the chore's own configuration change 
> handling.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to