hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4935) Manual leaving of safe mode may lead to data lost
Date Wed, 31 Dec 2008 01:18:44 GMT

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

Konstantin Shvachko updated HADOOP-4935:

      Resolution: Fixed
    Hadoop Flags: [Reviewed]
          Status: Resolved  (was: Patch Available)

I just committed this.

> Manual leaving of safe mode may lead to data lost
> -------------------------------------------------
>                 Key: HADOOP-4935
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4935
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.18.3
>            Reporter: Hairong Kuang
>            Assignee: Konstantin Shvachko
>             Fix For: 0.18.3
>         Attachments: misReplBlocks-0-18.patch, misReplBlocks.patch
> Due to HADOOP-4610, NameNode calculates mis-replicated blocks when leaving safe mode
manually, where it clears the pending deletion queue before it does the calculation. This
works fine when NameNode just starts but introduced a bug when NameNode is running for a while.
Clearing the pending deletion queue makes NameNode not able to distinguish valid replicas
from invalid ones, ie, the ones that have scheduled or dispatched for deletion. Therefore,
NameNode may mistakenly decide the block is over-replicated and choose all valid ones to delete.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message