You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (Commented) (JIRA)" <ji...@apache.org> on 2011/10/21 07:22:33 UTC

[jira] [Commented] (HBASE-4643) Consider reverting HBASE-451 (change HRI to remove HTD) in 0.92

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

Ted Yu commented on HBASE-4643:
-------------------------------

Have we proven that no patch from HBASE-4388 works ?
Stack is half way through composing the test in HBASE-4388 which would allow replaying upgrade scenarios.

One major issue HBASE-451 solves is that too much heap is consumed on the master if the number of regions in the cluster is high.

If we really cannot get upgrade done (the chance is slim), we have the following alternative:
1. backup old /hbase hdfs tree
2. boot up 0.92 from clean hdfs
3. copy data prepared by step 1 to the same old location
3. use tool from HBASE-4377 to regenerate .META. table
                
> Consider reverting HBASE-451 (change HRI to remove HTD) in 0.92
> ---------------------------------------------------------------
>
>                 Key: HBASE-4643
>                 URL: https://issues.apache.org/jira/browse/HBASE-4643
>             Project: HBase
>          Issue Type: Brainstorming
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
>
> I've been chatting with some folks recently about this thought: it seems like, if you enumerate the larger changes in 0.92, this is probably the one that is the most destabilizing that hasn't been through a lot of "baking" yet. You can see this evidenced by the very high number of followup commits it generated: looks like somewhere around 15 of them, plus some bugs still open.
> I've done a patch to revert this and the related followup changes on the 0.92 branch. Do we want to consider doing this?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira