[
https://issues.apache.org/jira/browse/HBASE-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165945#comment-17165945
]
Michael Stack commented on HBASE-15519:
---------------------------------------
So, yeah, the per-user I think needs working on. For example, here is what I
see for connections... i.e. all from one 'user', the APP_USER, all lumped
together, though from different IPs....:
{code:java}
2020-07-27 17:21:49,576 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.189.210:33190, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:49,615 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.184.233:37032, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:49,992 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.188.92:42026, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:50,136 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.178.154:40568, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:50,894 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.185.40:59874, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:51,082 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.188.86:46592, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:51,470 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.181.25:56220, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:51,478 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.184.211:44888, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:51,644 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.185.34:45848, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:51,954 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.174.87:46344, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:52,342 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.191.23:40736, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:52,461 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.181.150:39626, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:52,494 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.186.83:44636, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:52,663 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.181.211:40950, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService
2020-07-27 17:21:52,996 INFO SecurityLogger.org.apache.hadoop.hbase.Server:
Connection from 192.192.184.147:37758, version=1.2.0, sasl=false, ugi=APP_NAME
(auth:SIMPLE), service=ClientService {code}
> 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)
