Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1028600536.1233623639726.JavaMail.jira@brutus>
Date: Mon, 2 Feb 2009 17:13:59 -0800 (PST)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Issue Comment Edited: (HADOOP-5158) Port HDFS space quotas
 to 0.18
In-Reply-To: <1122197890.1233616439716.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-5158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12669828#action_12669828 ] 

rangadi edited comment on HADOOP-5158 at 2/2/09 5:12 PM:
--------------------------------------------------------------

(Edit : minor readability fixes)
On further thought, it does not look like it is simple to handle the layout change. The layout version is 16 (namespace quotas) in 0.18. In 0.19, layout increased to 17 for access times and then to 18 for space quotas.

The layout version in 0.18 can not be changed as long as we support upgrade from 0.18.4 to already released versions like 0.19.0. Even if have a restriction like a software can only be upgraded to a later version (i.e. 0.18.4 to 0.19.1 (future release), but not to 0.19.0), the code could be a bit messy.

What can be done now? I think we could provide a work around where space quotas are not persistent in 0.18. So admin need to set the quotas each time the cluster restarts. Since quotas are not really used by many, this might be an acceptable work around for a very few who need it.

      was (Author: rangadi):
    On further thought, it does not look like it is simple to handle the layout change. The layout version is 16 (namespace quotas). In 0.19, layout increased to 17 for access times and then to 18 for space quotas.

The layout version in 0.18 can not be changed as long as we support upgrade to 0.18.4 to already released versions like 0.19.0. Even if have a restriction like a software can only be upgraded to a later verison (i.e. 0.18.4 to 0.19.1 (future release), but not to 0.19.0), the code could be a bit messy.

What can be done now? I think we could provide a work around where space quotas are not persistent in 0.18. So admin need to set the quotas each time the cluster restarts. Since quotas are not really used by many, this might be an acceptable work around for a very few who need it.
  
> Port HDFS space quotas to 0.18
> ------------------------------
>
>                 Key: HADOOP-5158
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5158
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.18.3
>            Reporter: Raghu Angadi
>            Assignee: Raghu Angadi
>
> 0.18 already has quotas for HDFS namespace (HADOOP-3187). HADOOP-3938 implements similar quotas for disk space on HDFS in 0.19. This jira proposes to port HADOOP-3938 to 0.18.4.

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