[
https://issues.apache.org/jira/browse/HDFS-15727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247977#comment-17247977
]
Kihwal Lee commented on HDFS-15727:
-----------------------------------
Standby namenode replays edits with the name system write lock held. Depending
on the transaction rate and tailing frequency, it can last a long time, even
more so with the retry cache on. During this time, most RPC calls are sitting
in the call queue and not processed. This can drive up the queue time high,
but is of no concern.
> RpcQueueTimeAvgTime of the NameNode increases after it becomes StandBy
> ----------------------------------------------------------------------
>
> Key: HDFS-15727
> URL: https://issues.apache.org/jira/browse/HDFS-15727
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs
> Affects Versions: 2.8.2
> Reporter: Aihua Xu
> Priority: Major
> Attachments: image-2020-12-10-13-30-44-288.png
>
>
> RpcQueueTimeAvgTime of the NameNode increases after it becomes StandBy. It
> will get resolved after it gets restarted. Seems there is something incorrect
> about this metrics.
> See the following graph, the NameNode becomes StandBy at 10:13 while
> RpcQueueTimeAvgTime increases instead.
> !image-2020-12-10-13-30-44-288.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
