ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMBARI-16278) Give more time for HBase system tables to be assigned
Date Sun, 19 Feb 2017 15:57:44 GMT

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

Ted Yu edited comment on AMBARI-16278 at 2/19/17 3:57 PM:
----------------------------------------------------------

This issue is fairly commonly encountered.
Adopting larger values as default would alleviate the problem.


was (Author: yuzhihong@gmail.com):
This issue is fairly commonly encountered.

Adopting larger values as default would alleviate the problem.

> Give more time for HBase system tables to be assigned
> -----------------------------------------------------
>
>                 Key: AMBARI-16278
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16278
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Ted Yu
>
> We have observed extended cluster downtime due to HBase system tables not being assigned
at cluster start up.
> The default values for the following two parameters are too low:
> hbase.regionserver.executor.openregion.threads (default: 3)
> hbase.master.namespace.init.timeout (default: 300000)
> We set hbase.regionserver.executor.openregion.threads=200 and hbase.master.namespace.init.timeout=2400000
in some case to work around HBASE-14190.
> Ambari can use 20 for hbase.regionserver.executor.openregion.threads and 2400000 for
hbase.master.namespace.init.timeout as default value.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message