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

Hudson commented on HBASE-15955:
--------------------------------

SUCCESS: Integrated in HBase-1.2-IT #523 (See 
[https://builds.apache.org/job/HBase-1.2-IT/523/])
HBASE-15955 Disable action in CatalogJanitor#setEnabled should wait for 
(syuanjiangdev: rev edbf2754a410d3a4496ba1c2c8f96c7919da50a8)
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/CatalogJanitor.java


> Disable action in CatalogJanitor#setEnabled should wait for active cleanup 
> scan to finish
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-15955
>                 URL: https://issues.apache.org/jira/browse/HBASE-15955
>             Project: HBase
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.0.0, 2.0.0
>            Reporter: Stephen Yuan Jiang
>            Assignee: Stephen Yuan Jiang
>             Fix For: 2.0.0, 1.3.0, 1.2.2, 1.1.6
>
>         Attachments: HBASE-15955.master-v1.patch
>
>
> When user calls Admin.enableCatalogJanitor(false) to disable the catalog 
> janitor, it expects that the janitor would stop working once the API returns. 
>  It is not true, the janitor could have an active scan going on and clean up 
> unused region.  The 'false' state would be enforced during the next 
> background runs.  
> To avoid confusing, if 'CatalogJanitor.enabled' is true and we want to set to 
> false in CatalogJanitor#setEnabled, the function should wait for the on-going 
> active scan to complete.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to