[jira] [Commented] (HBASE-24911) Configure a max global timeout for HMaster to wait for RS to check in

["Sandeep Guggilam (Jira)" <ji...@apache.org>]

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

Sandeep Guggilam commented on HBASE-24911:
------------------------------------------

FYI [~apurtell]

> Configure a max global timeout for HMaster to wait for RS to check in
> ---------------------------------------------------------------------
>
>                 Key: HBASE-24911
>                 URL: https://issues.apache.org/jira/browse/HBASE-24911
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Sandeep Guggilam
>            Assignee: Sandeep Guggilam
>            Priority: Minor
>
> As part of the initialization process for active master, it waits for region servers to check in before completing the initialization. Currently it runs into a loop where it waits in the loop for ever when there are no region servers that are reported to it ([https://github.com/apache/hbase/blob/branch-1/hbase-server/src/main/java/org/apache/hadoop/hbase/master/ServerManager.java#L1126)]
>  
> We should probably have a global max timeout after which the master should give up and abort itself letting other masters to take over as active master . This is especially useful in the cases where the incoming connections to the master are not accepted because of network issue



--
This message was sent by Atlassian Jira
(v8.3.4#803005)