[
https://issues.apache.org/jira/browse/HBASE-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915841#comment-16915841
]
Sean Busbey commented on HBASE-15519:
-------------------------------------
this topic came up again in reviews of HBASE-11062.
I think we need testing with more users to see what the load on a RS looks
like. test with > 16 users, > 100 users, > 1000 users. test with long tail
users (like 4 users who are around a lot and then a few hundred who only show
up with freq < metric system refresh)
an implementation should be based on the lossy counting of top-X that got added
in HBASE-19722 / HBASE-21991.
> 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: Enis Soztutar
> Priority: Major
> Attachments: 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.2#803003)
