[
https://issues.apache.org/jira/browse/HBASE-25460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295677#comment-17295677
]
Hudson commented on HBASE-25460:
--------------------------------
Results for branch branch-2.2
[build #183 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/183/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/183//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/183//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/183//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/183//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Expose drainingServers as cluster metric
> ----------------------------------------
>
> Key: HBASE-25460
> URL: https://issues.apache.org/jira/browse/HBASE-25460
> Project: HBase
> Issue Type: New Feature
> Components: metrics
> Affects Versions: 1.6.0, 2.4.0
> Reporter: Viraj Jasani
> Assignee: Rahul Kumar
> Priority: Major
> Fix For: 3.0.0-alpha-1, 1.7.0, 2.2.7, 2.5.0, 2.3.5, 2.4.2
>
>
> Due to some reason, we had significantly high number of servers put in
> decommissioned mode and for significant time, they continued being in the
> same state serving no regions at all. This put heavy load on rest of live
> servers and it was too late before one could recognize the issues with
> improper balancing of the cluster. And as expected, balancing such cluster
> with/without *runMaxSteps* can bring up sudden spike of RITs in proportion to
> the degree of imbalanced regions in the cluster.
> Although running into such situation is rare, we can take some precautions by
> exposing metric. We should expose list of draining RegionServers as jmx
> metrics just like we expose _*liveRegionServers*_ and _*deadRegionServers*_.
> Such metric can help configure alerts with threshold on % of total RS that
> are allowed to go in draining mode (e.g during rolling upgrades) in any
> circumstances.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
