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 "Takanobu Asanuma (Jira)" <ji...@apache.org> on 2021/12/29 15:29:00 UTC

[jira] [Resolved] (HDFS-16348) Mark slownode as badnode to recover pipeline

     [ https://issues.apache.org/jira/browse/HDFS-16348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Takanobu Asanuma resolved HDFS-16348.
-------------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

> Mark slownode as badnode to recover pipeline
> --------------------------------------------
>
>                 Key: HDFS-16348
>                 URL: https://issues.apache.org/jira/browse/HDFS-16348
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Janus Chow
>            Assignee: Janus Chow
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>          Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> In HDFS-16320, the DataNode can retrieve the SLOW status from each NameNode. 
> This ticket is to send this information back to Clients who are writing blocks. If a Clients noticed the pipeline is build on a slownode, he/she can choose to mark the slownode as a badnode to exclude the node or rebuild a pipeline.
> In order to avoid the false positives, we added a config of "threshold", only clients continuously receives slownode reply from the same node will the node be marked as SLOW.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org