hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4010) HMaster.createTable could be heavily optimized
Date Wed, 22 Jun 2011 05:23:47 GMT

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

stack commented on HBASE-4010:
------------------------------

I was thinking of passing the hlog into HRegion constructor and just having HRegion deal with
a null hlog but not important.  We can do that in another issue.  This patch looks good to
me.  +1 on commit if tests pass.

> HMaster.createTable could be heavily optimized
> ----------------------------------------------
>
>                 Key: HBASE-4010
>                 URL: https://issues.apache.org/jira/browse/HBASE-4010
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.90.3
>            Reporter: Jean-Daniel Cryans
>            Assignee: Ted Yu
>             Fix For: 0.92.0
>
>         Attachments: 4010-v2.txt, 4010-v3.txt, 4010-v5.txt
>
>
> Looking at the createTable method in HMaster (the one that's private), we seem to be
very inefficient:
>  - We set the enabled flag for the table for every region (should be done only once).
>  - Every time we create a new region we create a new HLog and then close it (reuse one
instead or see if it's really necessary).
>  - We do one RPC to .META. per region (we should batch put).
> This should provide drastic speedups even for those creating tables with just 50 regions.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message