hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3586) Blocks are not getting replicate even DN's are availble.
Date Mon, 02 Jul 2012 22:40:58 GMT

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

Konstantin Shvachko commented on HDFS-3586:

Uma, I think that the RBW replicas on DN3 and DN4 should eventually be transformed into corrupt
replicas, because they should have a wrong generation stamp.
Then you are right it is similar to HDFS-3493. There is 4 nodes more than replication 3, but
there are no nodes that can be used to replicate the block to, because all have a replica
of the block.
I don't see how your suggestion solves the problem, as it doesn't work in case when all replicas
are corrupt, if I understand it correctly.
> 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: data-node, name-node
>    Affects Versions: 2.0.0-alpha, 2.0.1-alpha, 3.0.0
>            Reporter: Brahma Reddy Battula
>         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
> Here NN is asking replicate to DN3 and DN4,but it's failing since replcia's are already
present in RBW dir.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message