Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EF5F017436 for ; Sat, 26 Sep 2015 03:44:20 +0000 (UTC) Received: (qmail 52468 invoked by uid 500); 26 Sep 2015 03:44:20 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 52416 invoked by uid 500); 26 Sep 2015 03:44:20 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 52403 invoked by uid 99); 26 Sep 2015 03:44:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 Sep 2015 03:44:20 +0000 Date: Sat, 26 Sep 2015 03:44:20 +0000 (UTC) From: =?utf-8?Q?=E9=83=AD=E5=90=8C_=28JIRA=29?= To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-2576) Namenode should have a favored nodes hint to enable clients to have control over block placement. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-2576?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14909= 050#comment-14909050 ]=20 =E9=83=AD=E5=90=8C commented on HDFS-2576: -------------------------- I have the same problem,Thank you very much ... > Namenode should have a favored nodes hint to enable clients to have contr= ol over block placement. > -------------------------------------------------------------------------= ------------------------ > > Key: HDFS-2576 > URL: https://issues.apache.org/jira/browse/HDFS-2576 > Project: Hadoop HDFS > Issue Type: New Feature > Components: hdfs-client, namenode > Reporter: Pritam Damania > Assignee: Devaraj Das > Fix For: 2.1.0-beta > > Attachments: hdfs-2576-1.txt, hdfs-2576-trunk-1.patch, hdfs-2576-= trunk-2.patch, hdfs-2576-trunk-7.1.patch, hdfs-2576-trunk-7.patch, hdfs-257= 6-trunk-8.1.patch, hdfs-2576-trunk-8.2.patch, hdfs-2576-trunk-8.3.patch, hd= fs-2576-trunk-8.patch > > > Sometimes Clients like HBase are required to dynamically compute the data= nodes it wishes to place the blocks for a file for higher level of locality= . For this purpose there is a need of a way to give the Namenode a hint in = terms of a favoredNodes parameter about the locations where the client want= s to put each block. The proposed solution is a favored nodes parameter in = the addBlock() method and in the create() file method to enable the clients= to give the hints to the NameNode about the locations of each replica of t= he block. Note that this would be just a hint and finally the NameNode woul= d look at disk usage, datanode load etc. and decide whether it can respect = the hints or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)