You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Haibin Huang (Jira)" <ji...@apache.org> on 2020/03/17 04:21:00 UTC
[jira] [Commented] (HDFS-14783) expired SampleStat need to be
removed from SlowPeersReport
[ https://issues.apache.org/jira/browse/HDFS-14783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060623#comment-17060623 ]
Haibin Huang commented on HDFS-14783:
-------------------------------------
[~ayushtkn] [~elgoiri] , can you take a look for this, thanks.
> expired SampleStat need to be removed from SlowPeersReport
> ----------------------------------------------------------
>
> Key: HDFS-14783
> URL: https://issues.apache.org/jira/browse/HDFS-14783
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Haibin Huang
> Assignee: Haibin Huang
> Priority: Major
> Attachments: HDFS-14783, HDFS-14783-001.patch, HDFS-14783-002.patch
>
>
> SlowPeersReport is calculated by the SampleStat between tow dn, so it can present on nn's jmx like this:
> {code:java}
> "SlowPeersReport" :[{"SlowNode":"dn2","ReportingNodes":["dn1"]}]
> {code}
> the SampleStat is stored in a LinkedBlockingDeque<SumAndCount>, it won't be removed until the queue is full and a newest one is generated. Therefore, if dn1 don't send any packet to dn2 for a long time, the old SampleStat will keep staying in the queue, and will be used to calculated slowpeer.I think these old SampleStats should be considered as expired message and ignore them when generating a new SlowPeersReport.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org