You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrei Dragomir (JIRA)" <ji...@apache.org> on 2009/10/02 11:02:23 UTC

[jira] Commented: (HBASE-1832) Faster enable/disable/delete

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

Andrei Dragomir commented on HBASE-1832:
----------------------------------------

As I see in the HBaseAdmin, all the table modification operations go to the master, and everything there is synchronized on the RegionManager on the HMaster. Can we change these semantics ? What happens if client code disables the table while another client enables it ?

The second observation is that, there are about three or four different patterns in the code to scan the meta / get a table's regions (MetaScanner, MetaUtils, direct HTable(meta), etc). I think it would be better to have only one pattern.



> Faster enable/disable/delete
> ----------------------------
>
>                 Key: HBASE-1832
>                 URL: https://issues.apache.org/jira/browse/HBASE-1832
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>             Fix For: 0.20.1
>
>
> The enable/disable/delete is slow.  Looking at code, its heavyweight.  It doesn't do bulk scanning nor bulk writing.  Try doing some code client side that does bulk scan and bulk puts.  It might run faster. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.