You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jeffrey Zhong (JIRA)" <ji...@apache.org> on 2014/03/25 22:15:15 UTC
[jira] [Created] (HBASE-10833) Region assignment may fail during
cluster start up
Jeffrey Zhong created HBASE-10833:
-------------------------------------
Summary: Region assignment may fail during cluster start up
Key: HBASE-10833
URL: https://issues.apache.org/jira/browse/HBASE-10833
Project: HBase
Issue Type: Bug
Components: Region Assignment
Reporter: Jeffrey Zhong
Assignee: Jeffrey Zhong
This is an intermittent & infrequent issue. It happens when a cluster is starting up, only when one region server is available for region assignment temporally and master has a transient issue to talk to the only RS
When the RPC layer has a hiccup to talk to a RS, the RS will be put in failed server list and it will stay in failed server list for 2 sec(default value).
While the 20 region retires completes much shorter than 2 secs, the end result is a failed assignment.
Below are the logging for the total time spent on 20 assignment retires, it only took about 36 ms for all the retries.
{code}
2014-03-24 18:14:43,451 WARN [AM.ZK.Worker-pool2-t59] master.AssignmentManager: Failed assignment of hbase:labels,,1395668310177.f7372ede6c8bd7de4e91bfeda884cffb. to hor15n18.gq1.ygridcore.net,60020,1395684489232, trying to assign elsewhere instead; try=1 of 20
….
2014-03-24 18:14:43,487 WARN [AM.ZK.Worker-pool2-t59] master.AssignmentManager: Failed assignment of hbase:labels,,1395668310177.f7372ede6c8bd7de4e91bfeda884cffb. to hor15n18.gq1.ygridcore.net,60020,1395684489232, trying to assign elsewhere instead; try=20 of 20
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)