You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/11/16 20:42:59 UTC

[jira] [Resolved] (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:all-tabpanel ]

stack resolved HBASE-4246.
--------------------------
    Resolution: Won't Fix

Resolving as stale, no-longer-pertinent. Reopen if still issue in more modern hbase.

> 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 was sent by Atlassian JIRA
(v6.3.4#6332)