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

Kihwal Lee resolved HDFS-6964.
------------------------------
    Resolution: Duplicate

> NN fails to fix under replication leading to data loss
> ------------------------------------------------------
>
>                 Key: HDFS-6964
>                 URL: https://issues.apache.org/jira/browse/HDFS-6964
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.0.0-alpha, 3.0.0-alpha1
>            Reporter: Daryn Sharp
>            Priority: Blocker
>
> We've encountered lost blocks due to node failure even when there is ample 
> time to fix the under-replication.
> 2 nodes were lost.  The 3rd node with the last remaining replicas averaged 1 
> copy block per heartbeat (3s) until ~7h later when that node was lost 
> resulting in over 50 lost blocks.  When the node was restarted and sent its 
> BR the NN immediately began fixing the replication.
> In another data loss event, over 150 blocks were lost due to node failure but 
> the timing of the node loss is not known so there may have been inadequate 
> time to fix the under-replication unlike the first case.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org

Reply via email to