[
https://issues.apache.org/jira/browse/HDFS-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133677#comment-14133677
]
Vinayakumar B commented on HDFS-3586:
-------------------------------------
Hi [~usrikanth],
yes you are right.. HDFS-3493 solves the above issue. this jira can be resolved
as duplicate.
as mentioned in HDFS-3493 changes, in following cases corrupt replica will be
deleted.
{code}
// case 1: have enough number of live replicas
// case 2: corrupted replicas + live replicas > Replication factor
// case 3: Block is marked corrupt due to failure while writing. In this
// case genstamp will be different than that of valid block.
// In all these cases we can delete the replica.
// In case of 3, rbw block will be deleted and valid block can be replicated
{code}
> 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)
