Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1245279276.1224634004264.JavaMail.jira@brutus>
Date: Tue, 21 Oct 2008 17:06:44 -0700 (PDT)
From: "Robert Chansler (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3732) Block scanner should read block
 information during initialization.
In-Reply-To: <2025956983.1215629011674.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Chansler updated HADOOP-3732:
------------------------------------

    Release Note:   (was: Delay intialization of datanode block verification till the verification thread is started.
)

> Block scanner should read block information during initialization.
> ------------------------------------------------------------------
>
>                 Key: HADOOP-3732
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3732
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.17.0
>            Reporter: Konstantin Shvachko
>            Assignee: Raghu Angadi
>            Priority: Blocker
>             Fix For: 0.19.0
>
>         Attachments: HADOOP-3732.patch, HADOOP-3732.patch
>
>
> We see a lot of warning messages on each data-node during startup and upgrading from 0.17 to 0.18 saying:
> {code}
> 2008-07-08 22:22:15,711 WARN org.apache.hadoop.dfs.DataNode: Block /grid/3/hadoop/var/hdfs/data/current/blk_3359714082706415785 does not have a metafile!
> {code}
> The message received twice for each block, because the block information is first read buy the data-node itself and then by the block scanner.

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