hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4556) Block went missing
Date Mon, 10 Nov 2008 19:39:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646332#action_12646332

Raghu Angadi commented on HADOOP-4556:

> 2. When removing a datanode, reset its scheduled invalidate blocks.

There is also 'recentIvalidateSets'. When NN deletes a block, it first goes into 'recentInvalidateSets',
then the replication monitor thread moves this request to datanode's invalidateSet. I don't
know why we have this two step process, but looks like this patch needs to clear the datanode's
set in recentInvalidateSets as well.

I don't think 'addToInvalidatesNoLog' is necessary. The extra log is fine and will make it
consistent as well.

> Block went missing
> ------------------
>                 Key: HADOOP-4556
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4556
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.17.2
>            Reporter: Robert Chansler
>            Assignee: Hairong Kuang
>             Fix For: 0.18.3
>         Attachments: missing-block-example.txt, staleInvalidates.patch, staleInvalidates1.patch
> Suspicion that all replicas of a block were marked for deletion. (Don't panic, investigation

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

View raw message