[
https://issues.apache.org/jira/browse/HBASE-13403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Esteban Gutierrez updated HBASE-13403:
--------------------------------------
Resolution: Invalid
Release Note: (was: Now is possible to configure for how long the HBase
Master will wait until the NameNode leaves the safe mode:
hbase.master.waitonsafemode (in milliseconds) For backward compatibility
purposes we fallback to the previous value defined by
hbase.server.thread.wakefrequency (10000 milliseconds) if
hbase.master.waitonsafemode is not defined.)
Status: Resolved (was: Patch Available)
> Make waitOnSafeMode configurable in MasterFileSystem
> ----------------------------------------------------
>
> Key: HBASE-13403
> URL: https://issues.apache.org/jira/browse/HBASE-13403
> Project: HBase
> Issue Type: Bug
> Components: master
> Reporter: Esteban Gutierrez
> Assignee: Esteban Gutierrez
> Priority: Minor
> Attachments:
> 0001-HBASE-13403-Make-waitOnSafeMode-configurable-in-Mast.patch,
> 0001-HBASE-13403-Make-waitOnSafeMode-configurable-in-Mast.patch
>
>
> We currently wait whatever is the configured value of
> hbase.server.thread.wakefrequency or the default 10 seconds. We should have a
> configuration to control how long we wait until the HDFS is no longer in safe
> mode, since using the existing hbase.server.thread.wakefrequency property to
> tune that can have adverse side effects. My proposal is to add a new property
> called hbase.master.waitonsafemode and start with the current default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
