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 "Ahmed Hussein (Jira)" <ji...@apache.org> on 2020/04/01 21:05:00 UTC
[jira] [Commented] (HDFS-14968) Add ability to know datanode
staleness
[ https://issues.apache.org/jira/browse/HDFS-14968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073180#comment-17073180 ]
Ahmed Hussein commented on HDFS-14968:
--------------------------------------
I did not see much slowdown from enabling the feature.
I opted to use a configuration since it is a new feature.
> Add ability to know datanode staleness
> --------------------------------------
>
> Key: HDFS-14968
> URL: https://issues.apache.org/jira/browse/HDFS-14968
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode, logging, namenode
> Reporter: Ahmed Hussein
> Assignee: Ahmed Hussein
> Priority: Minor
> Fix For: 3.3.0, 3.1.4, 3.2.2, 2.10.1
>
> Attachments: HDFS-14968.001.patch, HDFS-14968.002.patch, HDFS-14968.003.patch
>
>
> There is no way to know whether a DataNode was marked stale or no longer stale by the NameNode.
> It will be good to have the option to enable logging the DataNode staleness to figure out if the staleness was the reason behind remote reads. Therefore, analyze performance and decision making of the local vs remote reads.
>
--
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