Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <886065131.1141517081785.JavaMail.jira@ajax.apache.org>
Date: Sun, 5 Mar 2006 01:04:41 +0100 (CET)
From: "Mike Cafarella (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Updated: (HADOOP-26) DFS node choice doesn't take available
 space into account effectively
In-Reply-To: <1437738270.1139335557543.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Mike Cafarella updated HADOOP-26:
---------------------------------

    Attachment: patch.targetchoice


  Patch for this problem.


> DFS node choice doesn't take available space into account effectively
> ---------------------------------------------------------------------
>
>          Key: HADOOP-26
>          URL: http://issues.apache.org/jira/browse/HADOOP-26
>      Project: Hadoop
>         Type: Bug
>   Components: dfs
>     Reporter: Mike Cafarella
>     Assignee: Mike Cafarella
>  Attachments: patch.targetchoice
>
>   We used to have node-allocation be sensitive to available disk space.  It turned out that
> this was a little accident-prone and hard to debug on then-available machines, so I removed it.
>   DFS is mature enough now that this needs to come back and work properly.  A node with less
> than X bytes should never accept a new block for allocation.

-- 
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