[
https://issues.apache.org/jira/browse/HDFS-15727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aihua Xu updated HDFS-15727:
----------------------------
Description:
RpcQueueTimeAvgTime of the NameNode on port 8020 (the client RPC calls)
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!
was:
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!
> 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 on port 8020 (the client RPC calls)
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
