hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4388) Second start after migration from 90 to trunk crashes
Date Wed, 05 Oct 2011 23:58:29 GMT

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

Todd Lipcon commented on HBASE-4388:
------------------------------------

A few small comments:
- we should have a constant like META_MIGRATION_CURRENT_VERSION which maps to the most recent
- we can use this when we have completed migration
- it seems to make more sense to have the constants just be ints, and then convert the cell
contents to an int where we do the comparison, rather than have the constants be byte arrays
and use byte array comparison.
                
> Second start after migration from 90 to trunk crashes
> -----------------------------------------------------
>
>                 Key: HBASE-4388
>                 URL: https://issues.apache.org/jira/browse/HBASE-4388
>             Project: HBase
>          Issue Type: Bug
>          Components: master, migration
>    Affects Versions: 0.92.0
>            Reporter: Todd Lipcon
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 0.92.0
>
>         Attachments: 4388-v2.txt, 4388-v3.txt, 4388.txt, meta.tgz
>
>
> I started a trunk cluster to upgrade from 90, inserted a ton of data, then did a clean
shutdown. When I started again, I got the following exception:
> 11/09/13 12:29:09 INFO master.HMaster: Meta has HRI with HTDs. Updating meta now.
> 11/09/13 12:29:09 FATAL master.HMaster: Unhandled exception. Starting shutdown.
> java.lang.NegativeArraySizeException: -102
>         at org.apache.hadoop.hbase.util.Bytes.readByteArray(Bytes.java:147)
>         at org.apache.hadoop.hbase.HTableDescriptor.readFields(HTableDescriptor.java:606)
>         at org.apache.hadoop.hbase.migration.HRegionInfo090x.readFields(HRegionInfo090x.java:641)
>         at org.apache.hadoop.hbase.util.Writables.getWritable(Writables.java:133)
>         at org.apache.hadoop.hbase.util.Writables.getWritable(Writables.java:103)
>         at org.apache.hadoop.hbase.util.Writables.getHRegionInfoForMigration(Writables.java:228)
>         at org.apache.hadoop.hbase.catalog.MetaEditor.getHRegionInfoForMigration(MetaEditor.java:350)
>         at org.apache.hadoop.hbase.catalog.MetaEditor$1.visit(MetaEditor.java:273)
>         at org.apache.hadoop.hbase.catalog.MetaReader.fullScan(MetaReader.java:633)
>         at org.apache.hadoop.hbase.catalog.MetaReader.fullScan(MetaReader.java:255)
>         at org.apache.hadoop.hbase.catalog.MetaReader.fullScan(MetaReader.java:235)
>         at org.apache.hadoop.hbase.catalog.MetaEditor.updateMetaWithNewRegionInfo(MetaEditor.java:284)
>         at org.apache.hadoop.hbase.catalog.MetaEditor.migrateRootAndMeta(MetaEditor.java:298)
>         at org.apache.hadoop.hbase.master.HMaster.updateMetaWithNewHRI(HMaster.java:529)
>         at org.apache.hadoop.hbase.master.HMaster.finishInitialization(HMaster.java:472)
>         at org.apache.hadoop.hbase.master.HMaster.run(HMaster.java:309)

--
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

        

Mime
View raw message