[ 
https://issues.apache.org/jira/browse/HDFS-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126903#comment-14126903
 ] 

Srikanth Upputuri commented on HDFS-3586:
-----------------------------------------

HDFS-3493 resolves the same issue. Now if the number of live replicas are more 
than minimum required and total replicas (live+corrupt) is more than 
replication factor, we invalidate the extra corrupt replica(s). Also, if the 
replica happens to be one that was discarded during a pipeline recovery, this 
will be invalidated if there are minimum number of live replicas irrespective 
of total replica count.

However, there is one possibility that can result in NN sending replication 
requests to copy a block to a DN with a write-pipeline-failed-replica. This is 
if the block is still being written when the reconnected DN sends a block 
report with an RBW/RWR replica for this block. I discussed this scenario in 
more detail in HDFS-2932. But for this situation, I think this jira can be 
closed as a duplicate to HDFS-3493. Please suggest.

> Blocks are not getting replicate even DN's are availble.
> --------------------------------------------------------
>
>                 Key: HDFS-3586
>                 URL: https://issues.apache.org/jira/browse/HDFS-3586
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode, namenode
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Brahma Reddy Battula
>            Assignee: amith
>         Attachments: HDFS-3586-analysis.txt
>
>
> Scenario:
> =========
> Started four DN's(Say DN1,DN2,DN3 and DN4)
> writing files with RF=3..
> formed pipeline with DN1->DN2->DN3.
> Since DN3 network is very slow.it's not able to send acks.
> Again pipeline is fromed with DN1->DN2->DN4.
> Here DN4 network is also slow.
> So finally commitblocksync happend tp DN1 and DN2 successfully.
> block present in all the four DN's(finalized state in two DN's and rbw state 
> in another DN's)..
> Here NN is asking replicate to DN3 and DN4,but it's failing since replcia's 
> are already present in RBW dir.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to