Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <17487886.1150197210625.JavaMail.jira@brutus>
Date: Tue, 13 Jun 2006 11:13:30 +0000 (GMT+00:00)
From: "Johan Oskarson (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-296) Do not assign blocks to a datanode
 with < x mb free
In-Reply-To: <12462846.1150196369845.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/HADOOP-296?page=all ]

Johan Oskarson updated HADOOP-296:
----------------------------------

    Attachment: minspace.patch

This is a completely untested patch, in fact it's more of an indication of what I mean with this feature request.
(I don't have the time nor the setup to test this right now)
Just thought I'd get this submitted before I forget

> Do not assign blocks to a datanode with < x mb free
> ---------------------------------------------------
>
>          Key: HADOOP-296
>          URL: http://issues.apache.org/jira/browse/HADOOP-296
>      Project: Hadoop
>         Type: New Feature

>   Components: dfs
>     Versions: 0.3.2
>     Reporter: Johan Oskarson
>  Attachments: minspace.patch
>
> We're running a smallish cluster with very different machines, some with only 60 gb harddrives
> This creates a problem when inserting files into the dfs, these machines run out of space quickly and then they cannot run any map reduce operations
> A solution would be to not assign any new blocks once the space is below a certain user configurable threshold
> This free space could then be used by the map reduce operations instead (if that's on the same disk)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira