You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ankit Singhal (Jira)" <ji...@apache.org> on 2019/09/19 23:44:00 UTC

[jira] [Commented] (HBASE-15519) Add per-user metrics

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

Ankit Singhal commented on HBASE-15519:
---------------------------------------

[~busbey], attaching forward port of the v2 patch and adding lossy counting for the user metrics. 003.patch is on top of HBASE-23054.
{quote}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)
{quote}
Let me know if we still need scale testing when lossyCounting is implemented.

> 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.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)