[
https://issues.apache.org/jira/browse/HBASE-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17164471#comment-17164471
]
Josh Elser commented on HBASE-15519:
------------------------------------
{quote}I see instances of 40 threads which seems a bunch for counting. In my
prod situation, there's a steady 140+ threads doing lossycounting which is a
bit over the top.
{quote}
Yeah, that seems over-kill. Off by default is fine to resolve quickly, IMO
Your data being shared here is great, Stack (2-3M metrics, 35-45MBeans). As
much data you can give to make a representative "at-scale" would help in making
we don't fall into the same trap would be great. Ideally, we come back here and
clean this up and make it OK for on-by-default.
> Add per-user metrics
> ---------------------
>
> Key: HBASE-15519
> URL: https://issues.apache.org/jira/browse/HBASE-15519
> Project: HBase
> Issue Type: Sub-task
> Components: metrics
> Affects Versions: 1.2.0
> Reporter: Enis Soztutar
> Assignee: Ankit Singhal
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0
>
> Attachments: HBASE-15519.master.003.patch, hbase-15519_v0.patch,
> hbase-15519_v1.patch, hbase-15519_v1.patch, hbase-15519_v2.patch
>
>
> Per-user metrics will be useful in multi-tenant cases where we can emit
> number of requests, operations, num RPCs etc at the per-user aggregate level
> per regionserver. We currently have throttles per user, but no way to monitor
> resource usage per-user.
> Looking at these metrics, operators can adjust throttles, do capacity
> planning, etc per-user.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
