[jira] [Commented] (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:comment-tabpanel=17109273#comment-17109273
]
Hudson commented on HBASE-23702:
Results for branch branch-2
[build #2664 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2664/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2664/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2664/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2664/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2664/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {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 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] [Commented] (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:comment-tabpanel=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 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] [Commented] (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:comment-tabpanel=17108364#comment-17108364
]
Hudson commented on HBASE-23702:
Results for branch master
[build #1728 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1728/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1728/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1663//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1728/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1728/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {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 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] [Commented] (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:comment-tabpanel=17108346#comment-17108346
]
Hudson commented on HBASE-23702:
Results for branch branch-2.3
[build #89 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/89/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/89/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/89/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/89/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/89/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {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 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] [Commented] (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:comment-tabpanel=17107063#comment-17107063 ] Guanghao Zhang commented on HBASE-23702: [~anoop.hbase] Added log in https://github.com/apache/hbase/pull/1703 > `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 >Assignee: 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] [Commented] (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:comment-tabpanel=17106258#comment-17106258 ] Anoop Sam John commented on HBASE-23702: bq.I think it could be better to provide some log information to let users know about the auto-correction behaviour. Or adding information in parameter description could also help user to better understand the situation The patch is not having this 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-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] [Commented] (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:comment-tabpanel=17106012#comment-17106012 ] Guanghao Zhang commented on HBASE-23702: [~ctest.team] Can you upload a patch generated by git format-patch? Then the patch will have your information. > `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] [Commented] (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:comment-tabpanel=17106009#comment-17106009 ] Guanghao Zhang commented on HBASE-23702: +1 > `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] [Commented] (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:comment-tabpanel=17057412#comment-17057412 ] Ctest commented on HBASE-23702: --- [~zghao] I think "at least one handler" is a good solution. I have uploaded a new patch. I think it could be better to provide some log information to let users know about the auto-correction behaviour. Or adding information in parameter description could also help user to better understand the situation. Do you have any suggestion? I am glad to provide the 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] [Commented] (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:comment-tabpanel=17049960#comment-17049960
]
Guanghao Zhang commented on HBASE-23702:
How about at least one handler? int handlerCount = Math.max(1,
conf.getInt("hbase.hstore.flusher.count", 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
>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] [Commented] (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:comment-tabpanel=17040538#comment-17040538
]
HBase QA commented on HBASE-23702:
--
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 3m
48s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:orange}-0{color} | {color:orange} test4tests {color} | {color:orange}
0m 0s{color} | {color:orange} The patch doesn't appear to include any new or
modified tests. Please justify why no new tests are needed for this patch. Also
please list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
45s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
6s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
34s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 4m
33s{color} | {color:blue} Used deprecated FindBugs config; considering
switching to SpotBugs. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
32s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
8s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
17m 36s{color} | {color:green} Patch does not cause any errors with Hadoop
2.8.5 2.9.2 or 3.1.2. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
48s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 91m
54s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
23s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}156m 11s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.6 Server=19.03.6 base:
https://builds.apache.org/job/PreCommit-HBASE-Build/1135/artifact/patchprocess/Dockerfile
|
| JIRA Issue | HBASE-23702 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12993944/HBASE-23702-000.patch
|
| Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs
shadedjars hadoopcheck hbaseanti checkstyle compile |
| uname | Linux c950adc66ddb 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19
08:06:28 UTC 2019 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/hbase-personality.sh |
| git revision | master / 53afc1dc10 |
| Default Java | 1.8.0_181 |
| Test Results |
https://builds.apache.org/job/PreCommit-HBASE-Build/1135/testReport/ |
|
[jira] [Commented] (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:comment-tabpanel=17038693#comment-17038693
]
HBase QA commented on HBASE-23702:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
38s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:orange}-0{color} | {color:orange} test4tests {color} | {color:orange}
0m 0s{color} | {color:orange} The patch doesn't appear to include any new or
modified tests. Please justify why no new tests are needed for this patch. Also
please list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
7s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
41s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 4m
19s{color} | {color:blue} Used deprecated FindBugs config; considering
switching to SpotBugs. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
16s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
4s{color} | {color:red} hbase-server: The patch generated 2 new + 21 unchanged
- 0 fixed = 23 total (was 21) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
39s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
15m 32s{color} | {color:green} Patch does not cause any errors with Hadoop
2.8.5 2.9.2 or 3.1.2. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
22s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 64m
5s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
34s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}119m 52s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.6 Server=19.03.6 base:
https://builds.apache.org/job/PreCommit-HBASE-Build/1132/artifact/patchprocess/Dockerfile
|
| JIRA Issue | HBASE-23702 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12993723/HBASE-23702-000.patch
|
| Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs
shadedjars hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 61f085826cf4 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6
11:12:41 UTC 2019 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/hbase-personality.sh |
| git revision | master / e11dbf36a5 |
| Default Java | 1.8.0_181 |
| checkstyle |
[jira] [Commented] (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:comment-tabpanel=17038033#comment-17038033
]
HBase QA commented on HBASE-23702:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 1m
11s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:orange}-0{color} | {color:orange} test4tests {color} | {color:orange}
0m 0s{color} | {color:orange} The patch doesn't appear to include any new or
modified tests. Please justify why no new tests are needed for this patch. Also
please list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
41s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
57s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
12s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
4s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 4m
42s{color} | {color:blue} Used deprecated FindBugs config; considering
switching to SpotBugs. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
41s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
12s{color} | {color:red} hbase-server: The patch generated 2 new + 21 unchanged
- 0 fixed = 23 total (was 21) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch has 1 line(s) that end in whitespace. Use git
apply --whitespace=fix <>. Refer https://git-scm.com/docs/git-apply
{color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
7s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
17m 19s{color} | {color:green} Patch does not cause any errors with Hadoop
2.8.5 2.9.2 or 3.1.2. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
49s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 95m 43s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
25s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}157m 15s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestAsyncTableGetMultiThreaded |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.6 Server=19.03.6 base:
https://builds.apache.org/job/PreCommit-HBASE-Build/1131/artifact/patchprocess/Dockerfile
|
| JIRA Issue | HBASE-23702 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12993613/HBASE-23702-000.patch
|
| Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs
shadedjars hadoopcheck hbaseanti checkstyle compile |
| uname | Linux af652754538f 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19
08:06:28 UTC 2019 x86_64 GNU/Linux
[jira] [Commented] (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:comment-tabpanel=17018528#comment-17018528
]
HBase QA commented on HBASE-23702:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 1m
17s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:orange}-0{color} | {color:orange} test4tests {color} | {color:orange}
0m 0s{color} | {color:orange} The patch doesn't appear to include any new or
modified tests. Please justify why no new tests are needed for this patch. Also
please list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
33s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
0s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
33s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 4m
58s{color} | {color:blue} Used deprecated FindBugs config; considering
switching to SpotBugs. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
56s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
57s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
12s{color} | {color:red} hbase-server: The patch generated 3 new + 21 unchanged
- 0 fixed = 24 total (was 21) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch 4 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
3s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
17m 17s{color} | {color:green} Patch does not cause any errors with Hadoop
2.8.5 2.9.2 or 3.1.2. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
35s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 5m
5s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}164m 51s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}226m 27s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.master.TestMasterShutdown |
| | hadoop.hbase.master.assignment.TestRegionMoveAndAbandon |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.5 Server=19.03.5 base:
https://builds.apache.org/job/PreCommit-HBASE-Build/1091/artifact/patchprocess/Dockerfile
|
| JIRA Issue | HBASE-23702 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12991282/HBASE-23702-000.patch
|
| Optional Tests | dupname asflicense javac javadoc unit spotbugs findbugs
shadedjars hadoopcheck hbaseanti checkstyle compile |
| uname | Linux d2f807e70001 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19
08:06:28 UTC 2019 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Commented] (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:comment-tabpanel=17017661#comment-17017661
]
HBase QA commented on HBASE-23702:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 2m
8s{color} | {color:blue} Docker mode activated. {color} |
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
10s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/in-progress/precommit-patchnames for
instructions. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m
0s{color} | {color:green} No case conflicting files found. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:orange}-0{color} | {color:orange} test4tests {color} | {color:orange}
0m 0s{color} | {color:orange} The patch doesn't appear to include any new or
modified tests. Please justify why no new tests are needed for this patch. Also
please list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
26s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
54s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
35s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
34s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 4m
33s{color} | {color:blue} Used deprecated FindBugs config; considering
switching to SpotBugs. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
32s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
58s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
54s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
18s{color} | {color:red} hbase-server: The patch generated 3 new + 21 unchanged
- 0 fixed = 24 total (was 21) {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch 4 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
34s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
15m 31s{color} | {color:green} Patch does not cause any errors with Hadoop
2.8.5 2.9.2 or 3.1.2. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
34s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
44s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}157m 29s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
33s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}215m 54s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.master.assignment.TestRegionMoveAndAbandon |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.5 Server=19.03.5 base:
https://builds.apache.org/job/PreCommit-HBASE-Build/1088/artifact/patchprocess/Dockerfile
|
| JIRA Issue | HBASE-23702 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12991179/hbase-src-patch.txt |
| Optional Tests | dupname asflicense javac
