[
https://issues.apache.org/jira/browse/HDFS-14406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812451#comment-16812451
]
Daryn Sharp commented on HDFS-14406:
------------------------------------
I'd also prefer this be optional. The overhead will provide little of the
intended value if intended for hdfs. Processing time for hdfs ops includes lock
wait time which unfairly inflates processing time for all ops. Ie. If one
user performs many write operations, all users are billed for the lock wait
time while the write ops complete. (Note: this may change soon if my internal
patch to exclude lock wait from processing time for the decay scheduler proves
successful)
Other than that, the following: "One metrics is exposed" should be "A metric is
exposed".
> 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
>
>
> 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
