[
https://issues.apache.org/jira/browse/HDFS-14406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822267#comment-16822267
]
Xue Liu commented on HDFS-14406:
--------------------------------
[~xkrogen] Makes sense to me, I will go back to per user metrics for this jira.
Though I don't believe volume will be a blocking factor. We have metrics like
NameNodeInfo via jmx give us all info on LiveNode and DeadNode, which is in the
scale of thousands. And in a large system we would have parsing wherever we
collect them, so I am not worried about readability either.
[~csun] Since we are only talking about per user metrics here, which approach
you think is better?
we can pass a flag to RpcDetailedMetrics, and add different prefix accordingly,
or we just create another metrics class?
> Add per user RPC Processing time
> --------------------------------
>
> Key: HDFS-14406
> URL: https://issues.apache.org/jira/browse/HDFS-14406
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 3.2.0
> Reporter: Xue Liu
> Assignee: Xue Liu
> Priority: Minor
> Fix For: 3.2.0
>
> Attachments: HDFS-14406.001.patch, HDFS-14406.002.patch,
> HDFS-14406.003.patch, HDFS-14406.004.patch, HDFS-14406.005.patch,
> HDFS-14406.006.patch
>
>
> For a shared cluster we would want to separate users' resources, as well as
> having our metrics reflecting on the usage, latency, etc, for each user.
> This JIRA aims to add per user RPC processing time metrics and expose it via
> JMX.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
