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

Hudson commented on HBASE-25854:
--------------------------------

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

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/285/General_20Nightly_20Build_20Report/]






(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/285/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/285/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Remove redundant AM in-memory state changes in CatalogJanitor
> -------------------------------------------------------------
>
>                 Key: HBASE-25854
>                 URL: https://issues.apache.org/jira/browse/HBASE-25854
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Kyle Purtell
>            Assignee: Andrew Kyle Purtell
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3
>
>
> In CatalogJanitor we schedule GCRegionProcedure to clean up both filesystem 
> and in-memory state after a split, and GCMultipleMergedRegionsProcedure to do 
> the same for merges. 
> Both GCRegionProcedure and GCMultipleMergedRegionsProcedure clean up 
> in-memory state, but CatalogJanitor also does this redundantly just after 
> scheduling the procedures. 
> The cleanup should be done in only one place. Presumably we are using the 
> procedures to do it in a principled way.  This is least a nit, but probably a 
> source of future bugs. Remove the redundancy in CatalogJanitor and fix any 
> follow on issues, like test failures. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to