Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 12 Feb 2016 20:49:18 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12938924.1455310146000.41171.1455310158125@Atlassian.JIRA>
In-Reply-To: <JIRA.12938924.1455310146000@Atlassian.JIRA>
References: <JIRA.12938924.1455310146000@Atlassian.JIRA>
 <JIRA.12938924.1455310146070@arcas>
Subject: [jira] [Created] (HDFS-9802) Selectively save blocks to trash dir
 during rolling upgrades
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kihwal Lee created HDFS-9802:
--------------------------------

             Summary: Selectively save blocks to trash dir during rolling upgrades
                 Key: HDFS-9802
                 URL: https://issues.apache.org/jira/browse/HDFS-9802
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Kihwal Lee


Currently datanodes save any invalidated blocks to the trash directory during a rolling upgrade. Compared to the "previous" directory for full upgrade, the trash can grow quickly. This is especially true when blocks are created and then quickly deleted.

Since trash is mainly meant to be defense against faulty new namenode and used for rolling back, saving new blocks in trash does not add much value. If anything, datanodes run out of space quicker.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)