hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Helmling (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-451) Remove HTableDescriptor from HRegionInfo
Date Fri, 24 Jun 2011 22:25:47 GMT

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

Gary Helmling commented on HBASE-451:

@Ted, good digging.

I'm not very familiar with these changes, but it looks to me like the changes so far have
tried to pull HTableDescription handling out of HRegion.  So adding it back in to HRegion.createHRegion()
may be a step back.

I think I'd opt for trying to fix the tests to call FSUtils.createTableDescriptor() instead.
 Either in TestTableMapReduce.<init> or MultiRegionTable.preHBaseClusterSetup(), prior
to creating the table regions.  I think either of those would work.  I wonder how many other
HBaseTestCase subclasses may have problems as well.

> Remove HTableDescriptor from HRegionInfo
> ----------------------------------------
>                 Key: HBASE-451
>                 URL: https://issues.apache.org/jira/browse/HBASE-451
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, regionserver
>    Affects Versions: 0.2.0
>            Reporter: Jim Kellerman
>            Assignee: Subbu M Iyer
>            Priority: Critical
>             Fix For: 0.92.0
>         Attachments: 451-addendum.txt, 451_support_for_removing_HTD_from_HRI_trunk.txt,
HBASE-451-Fixed_broken_TestAdmin.patch, HBASE-451-Fixed_broken_TestAdmin1.patch, HBASE-451_-_First_draft_support_for_removing_HTD_from_HRI1.patch,
HBASE-451_-_Fourth_draft_support_for_removing_HTD_from_HRI.patch, HBASE-451_-_Second_draft_-_Remove_HTD_from_HRI.patch,
descriptors.txt, fixtestadmin.txt, pass_htd_on_region_construction.txt
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message