Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Wed, 9 Jul 2014 17:41:04 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12726376.1404927572975.9648.1404927664857@arcas>
In-Reply-To: <JIRA.12726376.1404927572975@arcas>
References: <JIRA.12726376.1404927572975@arcas>
Subject: [jira] [Created] (HDFS-6651) Deletion failure can leak inodes
 permanently.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kihwal Lee created HDFS-6651:
--------------------------------

             Summary: Deletion failure can leak inodes permanently.
                 Key: HDFS-6651
                 URL: https://issues.apache.org/jira/browse/HDFS-6651
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Kihwal Lee
            Priority: Critical


As discussed in HDFS-6618, if a deletion of tree fails in the middle, any collected inodes and blocks will not be removed from {{INodeMap}} and {{BlocksMap}}. 

Since fsimage is saved by iterating over {{INodeMap}}, the leak will persist across name node restart. Although blanked out inodes will not have reference to blocks, blocks will still refer to the inode as {{BlockCollection}}. As long as it is not null, blocks will live on. The leaked blocks from blanked out inodes will go away after restart.

Options (when delete fails in the middle)
- Complete the partial delete: edit log the partial delete and remove inodes and blocks. 
- Somehow undo the partial delete.
- Check quota for snapshot diff beforehand for the whole subtree.
- Ignore quota check during delete even if snapshot is present.


--
This message was sent by Atlassian JIRA
(v6.2#6252)