[
https://issues.apache.org/jira/browse/HDFS-16040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HDFS-16040:
---------------------------------------
Fix Version/s: 3.3.2
3.2.3
2.10.2
3.1.5
Hadoop Flags: Reviewed
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this to all active branches. Thank you, [~simbadzina].
> RpcQueueTime metric counts requeued calls as unique events.
> -----------------------------------------------------------
>
> Key: HDFS-16040
> URL: https://issues.apache.org/jira/browse/HDFS-16040
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 2.10.0, 3.3.0
> Reporter: Simbarashe Dzinamarira
> Assignee: Simbarashe Dzinamarira
> Priority: Major
> Fix For: 3.1.5, 2.10.2, 3.2.3, 3.3.2
>
> Attachments: HDFS-16040.001.patch, HDFS-16040.002.patch,
> HDFS-16040.003.patch
>
>
> The RpcQueueTime metric is updated every time a call is re-queued while
> waiting for the server state to reach the call's client's state ID. This is
> in contrast to RpcProcessingTime which is only updated when the call if
> finally processed.
> On the Observer NameNode this can result in RpcQueueTimeNumOps being much
> larger than RpcProcessingTimeNumOps. The re-queueing is an internal
> optimization to avoid blocking and shouldn't result in an inflated metric.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
