You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/01/16 19:24:13 UTC
[jira] [Commented] (HBASE-4246) Cluster with too many regions
cannot withstand some master failover scenarios
[ https://issues.apache.org/jira/browse/HBASE-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555296#comment-13555296 ]
stack commented on HBASE-4246:
------------------------------
I added a note to troubleshooting doc in the master startup section.
> 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
> Fix For: 0.96.0
>
>
> 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