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-2639) Bring root and meta over to new naming scheme (hbase-2531)
Date Tue, 01 Jun 2010 20:38:36 GMT

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

stack commented on HBASE-2639:
------------------------------

Here is a Kannan comment from tail of hbase-2531.

{code}
Todd/Stack: ROOT and the first META region are handled in a special hard-coded way in code.
See HRegionInfo::ROOT_REGIONINFO and HRegion::FIRST_META_REGIONINFO.

For example, their region id is hardcoded to 0 & 1 (and they do not use timestamps).

ROOT,,0
.META.,,1

Their Jenkins hash encoded names: 70236052 & 1028785192 respectively do not collide either.
Not changing this simplifies handling upgrade from an older version of HBase.

This should not be an issue for splits of META. If META splits, it should use the new format
region names (with timestamps for the region id portion) and md5 hash for encoded names.
{code}

Yea, they are done different to the rest and I was thinking later than when .META. splits,
it'll split in new style so there should be no clash of filesystem directory names.  I'll
leave this issue open though because it'd be best to have these align anyways if only to save
on the "why do these work different?" questions, down the road.

> Bring root and meta over to new naming scheme (hbase-2531)
> ----------------------------------------------------------
>
>                 Key: HBASE-2639
>                 URL: https://issues.apache.org/jira/browse/HBASE-2639
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>
> hbase-2531 introduced new region naming scheme.  root and meta were left using old scheme.
 This issue is about doing work to bring these over too.

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


Mime
View raw message