Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1549328498.1241730525710.JavaMail.jira@brutus>
Date: Thu, 7 May 2009 14:08:45 -0700 (PDT)
From: "Jakob Homan (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Assigned: (HADOOP-5099) DataNode should warn about unknown
 files in storage
In-Reply-To: <193504651.1232582879543.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-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakob Homan reassigned HADOOP-5099:
-----------------------------------

    Assignee: Jakob Homan

> DataNode should warn about unknown files in storage
> ---------------------------------------------------
>
>                 Key: HADOOP-5099
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5099
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Raghu Angadi
>            Assignee: Jakob Homan
>
> DataNode currently just ignores the files it does not know about. There could be a lot of files left in DataNode's storage that never get noticed or deleted. These files could be left because of bugs or by a misconfiguration. E.g. while upgrading from 0.17, DN left a lot of metada files that were not named in correct format for 0.18 (HADOOP-4663).
> The proposal here is simply to make DN print a warning for each of the unknown files at the start up. This at least gives a way to list all the unknown files and  (equally importantly) forces a notion of "known" and "unknown" files in the storage.

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