[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-23702: --- Resolution: Fixed Status: Resolved (was: Patch Available) Pushed to branch-2.2+. > `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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guanghao Zhang updated HBASE-23702: --- Fix Version/s: 2.2.5 2.3.0 3.0.0-alpha-1 Affects Version/s: (was: 2.2.3) > `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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Attachment: HBASE-23702-001.patch > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > 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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Attachment: HBASE-23702-000.patch > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > Attachments: HBASE-23702-000.patch, HBASE-23702-000.patch, > HBASE-23702-000.patch, HBASE-23702-000.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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Attachment: HBASE-23702-000.patch > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > Attachments: HBASE-23702-000.patch, HBASE-23702-000.patch, > HBASE-23702-000.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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Attachment: (was: hbase-src-patch.txt) > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > Attachments: HBASE-23702-000.patch, HBASE-23702-000.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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Attachment: HBASE-23702-000.patch > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > Attachments: HBASE-23702-000.patch, HBASE-23702-000.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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Attachment: (was: HBASE-ISSUEID-000.patch.txt) > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > Attachments: HBASE-23702-000.patch, HBASE-23702-000.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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Attachment: HBASE-23702-000.patch > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > Attachments: HBASE-23702-000.patch, HBASE-ISSUEID-000.patch.txt, > hbase-src-patch.txt > > > 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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Attachment: HBASE-ISSUEID-000.patch.txt > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > Attachments: HBASE-ISSUEID-000.patch.txt, hbase-src-patch.txt > > > 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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Description: 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 20ms ``` 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-- master -.log” was: *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 20ms ``` 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--master-.log” > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > Attachments: hbase-src-patch.txt > > > 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 20ms > ``` > > 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-- master -.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Description: *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 20ms ``` 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--master-.log” was: *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 20ms ``` 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 Hadoop: 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--master-.log” > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > Attachments: hbase-src-patch.txt > > > *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 20ms > ``` > > 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--master-.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HBASE-23702) `hbase.hstore.flusher.count` setting to 0 breaks HMaster
[ https://issues.apache.org/jira/browse/HBASE-23702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ctest updated HBASE-23702: -- Attachment: hbase-src-patch.txt Status: Patch Available (was: Open) > `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 >Affects Versions: 2.2.3 > Environment: HBase-2.2.3 > Java openjdk 1.8.0_222 > Ubuntu 18.04 >Reporter: Ctest >Priority: Major > Attachments: hbase-src-patch.txt > > > *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 20ms > ``` > > 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 Hadoop: 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--master-.log” -- This message was sent by Atlassian Jira (v8.3.4#803005)
