[jira] Commented: (HBASE-451) Remove HTableDescriptor from HRegionInfo

["Bryan Duxbury (JIRA)" <ji...@apache.org>]

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

Bryan Duxbury commented on HBASE-451:
-------------------------------------

If table descriptors lived in a .TABLE. table, would it be at the same level as user tables? 

Are there downsides to having a catalog table instead of storing in files? I'm not sure that the HBase-check thing is that big of an issue. The catalog table will almost always be pretty small, have a static name, and probably live in a pretty well known place. Even if META was corrupt, that wouldn't stop us from being able to recover the catalog table. (At least, not any more than it would stop us from recovering the rest of the user-level tables.)

> Remove HTableDescriptor from HRegionInfo
> ----------------------------------------
>
>                 Key: HBASE-451
>                 URL: https://issues.apache.org/jira/browse/HBASE-451
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.2.0
>            Reporter: Jim Kellerman
>            Priority: Minor
>             Fix For: 0.2.0
>
>
> There is an HRegionInfo for every region in HBase. Currently HRegionInfo also contains the HTableDescriptor (the schema). That means we store the schema n times where n is the number of regions in the table.
> Additionally, for every region of the same table that the region server has open, there is a copy of the schema. Thus it is stored in memory once for each open region.
> If HRegionInfo merely contained the table name the HTableDescriptor could be stored in a separate file and easily found.

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