Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 21 Oct 2014 16:54:35 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12737507.1409246780000.306763.1413910475139@Atlassian.JIRA>
In-Reply-To: <JIRA.12737507.1409246780000@Atlassian.JIRA>
References: <JIRA.12737507.1409246780000@Atlassian.JIRA>
 <JIRA.12737507.1409246780143@arcas>
Subject: [jira] [Updated] (HDFS-6964) NN fails to fix under replication
 leading to data loss
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kihwal Lee updated HDFS-6964:
-----------------------------
    Target Version/s: 2.7.0  (was: 2.6.0)

> 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
>            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.3.4#6332)