[jira] [Commented] (HBASE-10851) Wait for regionservers to join the cluster

["Demai Ni (JIRA)" <ji...@apache.org>]

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

Demai Ni commented on HBASE-10851:
----------------------------------

[~jxiang],

I encoutered this msg on master log on single-node cluster using trunk build "INFO org.apache.hadoop.hbase.master.ServerManager: Waiting for region servers count to settle; currently checked in 1, slept for 978938 ms, expecting *minimum of 2*, maximum of 2147483647, timeout of 4500 ms, interval of 1500 ms, selfCheckedIn true"

This jira change the default value to 2, and saw your comments "... The minimum regionservers to wait is changed from 1 to 2 so the active master is included. For standalone sever, the minimum regionservers to wait is set to 1."

After added property 'hbase.master.wait.on.regionservers.mintostart' into hbase-site.xml, and my cluster up and run again. 

My question is from migration/configuration perspective.  In the case an existing single-node cluster migrated to 1.0 (in my case, my cluster was using 98.2, I stopped hbase, replaced hbase jars, restarted hbase, and hit problem), is there a way to add such configuration into hbase-site.xml automatically? I examed the hbase-default.xml, and couldn't find the property, and also couldn't figure out whether we can use two different default values for single-node vs multi-node cluster.  

thanks

Demai




> Wait for regionservers to join the cluster
> ------------------------------------------
>
>                 Key: HBASE-10851
>                 URL: https://issues.apache.org/jira/browse/HBASE-10851
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Critical
>             Fix For: 0.99.0
>
>         Attachments: hbase-10851.patch, hbase-10851_v2.patch
>
>
> With HBASE-10569, if regionservers are started a while after the master, all regions will be assigned to the master.  That may not be what users expect.
> A work-around is to always start regionservers before masters.
> I was wondering if the master can wait a little for other regionservers to join.



--
This message was sent by Atlassian JIRA
(v6.2#6252)