hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4246) Cluster with too many regions cannot withstand some master failover scenarios
Date Tue, 23 Apr 2013 23:49:17 GMT

     [ https://issues.apache.org/jira/browse/HBASE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-4246:
-------------------------

    Fix Version/s:     (was: 0.95.1)

Not being worked on for 0.95.  Moving it out.  Leaving it around in case others run into the
issue so they can find the workaround.  We should also consider doing the suggested hierarcherying
(word?) in zk).
                
> Cluster with too many regions cannot withstand some master failover scenarios
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4246
>                 URL: https://issues.apache.org/jira/browse/HBASE-4246
>             Project: HBase
>          Issue Type: Bug
>          Components: master, Zookeeper
>    Affects Versions: 0.90.4
>            Reporter: Todd Lipcon
>
> We ran into the following sequence of events:
> - master startup failed after only ROOT had been assigned (for another reason)
> - restarted the master without restarting other servers. Since there was at least one
region assigned, it went through the failover code path
> - master scanned META and inserted every region into /hbase/unassigned in ZK.
> - then, it called "listChildren" on the /hbase/unassigned znode, and crashed with "Packet
len6080218 is out of range!" since the IPC response was larger than the default maximum.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message