[
https://issues.apache.org/jira/browse/HBASE-18652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162383#comment-16162383
]
Hadoop QA commented on HBASE-18652:
-----------------------------------
| (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:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m
4s{color} | {color:blue} The patch file was not named according to hbase's
naming conventions. Please see
https://yetus.apache.org/documentation/0.4.0/precommit-patchnames for
instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 7s{color}
| {color:red} HBASE-18652 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-18652 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12886560/18652-branch-1-V3.0.PATCH
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/8575/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Expose individual cache stats in a CombinedCache through JMX
> ------------------------------------------------------------
>
> Key: HBASE-18652
> URL: https://issues.apache.org/jira/browse/HBASE-18652
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Biju Nair
> Assignee: Biju Nair
> Fix For: 1.4.0, 1.5.0, 2.0.0-alpha-3
>
> Attachments: 18652-branch-1-V3.0.PATCH, HBASE-18652-addendum.patch,
> HBASE-18652-BRANCH-1.PATCH, HBASE-18652-branch-1-v1.0.patch,
> HBASE-18652-branch-1-V2.0.PATCH, HBASE-18652.PATCH, HBASE-18652-V1.0.PATCH,
> HBASE-18652-V2.0.PATCH, HBASE-18652-WIP.PATCH
>
>
> With offHeap cache being used to store data blocks and on-heap for index and
> bloom filters, exposing the stats from the individual caches through JMX will
> help understand the cache usage trend. Currently the combined cache stats is
> available through JMX which may not provide insight into the individual cache
> usage.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
