hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.Andreina (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2932) Under replicated block after the pipeline recovery.
Date Fri, 10 Feb 2012 13:36:59 GMT

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

J.Andreina commented on HDFS-2932:

Initially Three Dn was running ..but while writing the block (block-id-1005) i brought down
3rdDN.so the write was successful to other two DN but the block stamp was changed to (block-id-1006)
and the rest of the block was also written successfuly to those two datanodes.

After the write was over ,The 3rd DN was restarted after 5 mins.then when fsck command was
issued "block-id_1006 is underreplicatede.Target replicas is 3 but found 2 replicas" message
was displayed.

Ever after the replication monitor period is over ,the blocks is still  under replicated only.I
checked the same after 10 hrs. 
> Under replicated block after the pipeline recovery.
> ---------------------------------------------------
>                 Key: HDFS-2932
>                 URL: https://issues.apache.org/jira/browse/HDFS-2932
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>    Affects Versions: 0.24.0
>            Reporter: J.Andreina
>             Fix For: 0.24.0
> Started 1NN,DN1,DN2,DN3 in the same machine.
> Written a huge file of size 2 Gb
> while the write for the block-id-1005 is in progress bruought down DN3.
> after the pipeline recovery happened.Block stamp changed into block_id_1006 in DN1,Dn2.
> after the write is over.DN3 is brought up and fsck command is issued.
> the following mess is displayed as follows
> "block-id_1006 is underreplicatede.Target replicas is 3 but found 2 replicas".

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