You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/18 00:10:04 UTC

[jira] [Resolved] (HDFS-338) When a block is severely under replicated at creation time, a request for block replication should be scheduled immediately

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

Allen Wittenauer resolved HDFS-338.
-----------------------------------

    Resolution: Fixed

Closing this as stale.

> When a block is severely under replicated at creation time, a request for block replication should be scheduled immediately
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-338
>                 URL: https://issues.apache.org/jira/browse/HDFS-338
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Runping Qi
>
> During writing a block to data nodes, if the dfs client detects a bad data node in the write pipeline, it will re-construct a new data pipeline, 
> excluding the detected bad data node. This implies that when the client finishes writing the block, the number of the replicas for the block 
> may be lower than the intended replication factor. If the ratio of the number of replicas to the intended replication factor is lower than
> certain threshold (say 0.68), then the client should send a request to the name node to replicate that block immediately.



--
This message was sent by Atlassian JIRA
(v6.2#6252)