[
https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108586#comment-17108586
]
Hudson commented on HBASE-23702:
--------------------------------
Results for branch branch-2.2
[build #863 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/863/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/863//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/863//console].
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/862//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> `hbase.hstore.flusher.count` setting to 0 breaks HMaster
> --------------------------------------------------------
>
> Key: HBASE-23702
> URL: https://issues.apache.org/jira/browse/HBASE-23702
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Environment: HBase-2.2.3
> Java openjdk 1.8.0_222
> Ubuntu 18.04
> Reporter: Ctest
> Assignee: Ctest
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.5
>
> Attachments: HBASE-23702-000.patch, HBASE-23702-000.patch,
> HBASE-23702-000.patch, HBASE-23702-000.patch, HBASE-23702-001.patch
>
>
> Summary
> The configuration parameter `hbase.hstore.flusher.count` allows `0` (which
> turns out to be a bad value after I understand the source code).
> When we set `hbase.hstore.flusher.count` to 0, HMaster will fail in 200,000
> ms without any error message, but
> ```
> java.lang.RuntimeException: Master not initialized after 200000ms
> ```
>
> There’s no messages pinpointing `hbase.hstore.flusher.count` being the root
> cause.
>
> 0 means `MemStoreFlusher` is not alive. During the initialization time of
> HMaster, `isHealthy()` will be called and it will try to check if
> `MemStoreFlusher` is alive or not. However, since we set
> `hbase.hstore.flusher.count` to 0, there will be no flusher created at the
> first place, which cause`isHealthy()` to return false. As a consequence,
> HRegionServer does not enter its main loop.
>
> *How To Reproduce*
>
> The version of HBase: 2.2.3
>
> # Set the value of configuration parameter `hbase.hstore.flusher.count` to
> `0` in “conf/hbase-site.xml”
> # Start hbase by running “bin/start-hbase.sh”
> # Wait for 3-4 minutes
> # Open the log file “logs/hbase-<username>- master -<pcname>.log”
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
