[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[
https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[ https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007942#comment-17007942 ] Toshihiro Suzuki commented on HBASE-23065: -- I think this feature is very helpful for hbase administrators and we should backport to branch-1, too. > [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, 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)
[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[
https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002605#comment-17002605
]
Hudson commented on HBASE-23065:
Results for branch branch-2
[build #2394 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2394/]:
(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/branch-2/2394//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2394//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/branch-2/2394//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> [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, 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)
[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[ https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17002095#comment-17002095 ] Ankit Singhal commented on HBASE-23065: --- Now committed to branch-2 as well. Thank you guys for all the help and reviews. [~apurtell], Let me know if you want it for branch-1 too, I can create a Jira for the same. > [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, 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)
[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[ https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001599#comment-17001599 ] Toshihiro Suzuki commented on HBASE-23065: -- Sure. [~an...@apache.org] > [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 > > > 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)
[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[ https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000422#comment-17000422 ] Ankit Singhal commented on HBASE-23065: --- Sorry, couldn't commit as was travelling from last month. Thanks [~brfrn169] for taking care of it in my absence and merging it to master. Let me take a look for the changes required to merge it in branch-2 and commit it if they are minor otherwise I'll put up a patch for review. > [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 > > > 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)
[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[
https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16998250#comment-16998250
]
Hudson commented on HBASE-23065:
Results for branch master
[build #1570 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1570/]: (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/1570//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1570//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/1570//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> [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
>
>
> 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)
[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[ https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16997391#comment-16997391 ] Toshihiro Suzuki commented on HBASE-23065: -- Pushed to master. Trying to push to branch-2. It looks like we need some changes for this branch. > [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 > > > 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)
[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[ https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953410#comment-16953410 ] Toshihiro Suzuki commented on HBASE-23065: -- [~an...@apache.org] Will review this. Maybe I think I can do it by this weekend. > [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 > > 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)
[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[ https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953202#comment-16953202 ] Ankit Singhal commented on HBASE-23065: --- [~apurtell]/[~brfrn169]/[~busbey]/[~elserj], can anybody please help me with the review? > [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 > > 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)
[jira] [Commented] (HBASE-23065) [hbtop] Top-N heavy hitter user and client drill downs
[ https://issues.apache.org/jira/browse/HBASE-23065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936261#comment-16936261 ] Andrew Purtell commented on HBASE-23065: /cc [~brfrn169] [~busbey] [~xucang] [~lhofhansl] > [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 >Reporter: Andrew Purtell >Priority: Major > > 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 > out of many may be the source of the hot spotting load. -- This message was sent by Atlassian Jira (v8.3.4#803005)
