[ 
https://issues.apache.org/jira/browse/HBASE-18869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382575#comment-16382575
 ] 

Hadoop QA commented on HBASE-18869:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} 
| {color:red} HBASE-18869 does not apply to master. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.7.0/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-18869 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12891475/HBASE-18869.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/11757/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> Table rpc metrics
> -----------------
>
>                 Key: HBASE-18869
>                 URL: https://issues.apache.org/jira/browse/HBASE-18869
>             Project: HBase
>          Issue Type: Wish
>          Components: metrics
>    Affects Versions: 2.0.0-alpha-1
>            Reporter: Chenxi Tong
>            Priority: Minor
>              Labels: metrics
>         Attachments: HBASE-18869.patch
>
>
> Hi all
> In the HBASE-15518, uses the MetricsTableWrapperAggregateImpl to aggregate 
> each region`s 
> totalRequestsCount,readRequestsCount,writeRequestsCount,memstoresSize 
> storeFilesSize, tableSize metrics and exports them to jmx, so i want to use 
> the totalRequestsCount`rate as table`rpc request, but found it is bigger much 
> more than ServerLoad`s requestsPerSecond, i am not sure if it is a correct 
> way to do this, how we can collect each table`s rpc request?
> Best wishes!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to