[
https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17194573#comment-17194573
]
Hudson commented on HBASE-23065:
--------------------------------
Results for branch master
[build #44 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/44/]:
(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/master/44/General_20Nightly_20Build_20Report/]
(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/master/44/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/44/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {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/master/44//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> [hbtop] Top-N heavy hitter user and client drill downs
> ------------------------------------------------------
>
> Key: HBASE-23065
> URL: https://issues.apache.org/jira/browse/HBASE-23065
> Project: HBase
> Issue Type: Improvement
> Components: hbtop, Operability
> Reporter: Andrew Kyle Purtell
> Assignee: Ankit Singhal
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
>
> After HBASE-15519, or after an additional change on top of it that provides
> necessary data in ClusterStatus, add drill down top-N views of activity
> aggregated per user or per client IP. Only a relatively small N of the heavy
> hitters need be tracked assuming this will be most useful when one or a
> handful of users or clients is generating problematic load and hbtop is
> invoked to learn their identity.
> This is a critical missing piece. After drilling down to find hot regions or
> tables, sometimes that is not enough, we also need to know which application
> or subset of clients out of many may be the source of the hot spotting load.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
