hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1218) 20 append: Blocks recovered on startup should be treated with lower priority during block synchronization
Date Thu, 29 Mar 2012 01:19:26 GMT

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

Uma Maheswara Rao G commented on HDFS-1218:
-------------------------------------------

Thanks a lot Todd.

{quote}
However, it's still the case that DN3 might be shorter than the good replicas, and not included
in recovery. In that case, it should be deleted when it reports the block with the too-low
GS later. I guess the real issue is that we don't include all RBW blocks in block reports
in the 1.0 implementation, so it sticks around forever?
{quote}

Exactly.

{quote}
Since this issue has been closed a long time, mind opening a new one against branch-1? If
you could come up with a test case that would also be great. Seems like you could modify the
existing test cases just to make sure that the other replica eventually gets removed.
{quote}
Sure. I will file one new bug and come up with testcase.
                
> 20 append: Blocks recovered on startup should be treated with lower priority during block
synchronization
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-1218
>                 URL: https://issues.apache.org/jira/browse/HDFS-1218
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>    Affects Versions: 0.20-append
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Critical
>             Fix For: 0.20.205.0
>
>         Attachments: HDFS-1218.20s.2.patch, hdfs-1281.txt
>
>
> When a datanode experiences power loss, it can come back up with truncated replicas (due
to local FS journal replay). Those replicas should not be allowed to truncate the block during
block synchronization if there are other replicas from DNs that have _not_ restarted.

--
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

        

Mime
View raw message