Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D31DE200D3E for ; Thu, 16 Nov 2017 23:39:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D032C160BF4; Thu, 16 Nov 2017 22:39:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1FD131609EF for ; Thu, 16 Nov 2017 23:39:03 +0100 (CET) Received: (qmail 63783 invoked by uid 500); 16 Nov 2017 22:39:03 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 63769 invoked by uid 99); 16 Nov 2017 22:39:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Nov 2017 22:39:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 41CF11A127B for ; Thu, 16 Nov 2017 22:39:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id zzOmOCrhy8Q0 for ; Thu, 16 Nov 2017 22:39:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id F37215FC81 for ; Thu, 16 Nov 2017 22:39:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 83D3EE0A29 for ; Thu, 16 Nov 2017 22:39:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3A033240DA for ; Thu, 16 Nov 2017 22:39:00 +0000 (UTC) Date: Thu, 16 Nov 2017 22:39:00 +0000 (UTC) From: "Bharat Viswanadham (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HDFS-12827) Need Clarity on Replica Placement: The First Baby Steps in HDFS Architecture documentation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 16 Nov 2017 22:39:05 -0000 [ https://issues.apache.org/jira/browse/HDFS-12827?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1625= 6077#comment-16256077 ]=20 Bharat Viswanadham edited comment on HDFS-12827 at 11/16/17 10:38 PM: ---------------------------------------------------------------------- Hi [~surinuthalapati@live.com] In the latest design document, it is mentioned correctly {code:java} when the replication factor is three, HDFS=E2=80=99s placement policy is to= put one replica on the local machine if the writer is on a datanode, other= wise on a random datanode, another replica on a node in a different (remote= ) rack, and the last on a different node in the same remote rack {code} . http://hadoop.apache.org/docs/r3.0.0-beta1/hadoop-project-dist/hadoop-hdfs/= HdfsDesign.html Pls let me know any more is needed? was (Author: bharatviswa): Hi [~surinuthalapati@live.com] In the latest design document, it is mentioned correctly {code:java} when the replication factor is three, HDFS=E2=80=99s placement policy is to= put one replica on the local machine if the writer is on a datanode, other= wise on a random datanode, another replica on a node in a different (remote= ) rack, and the last on a different node in the same remote rack {code} . Pls let me know any more is needed? > Need Clarity on Replica Placement: The First Baby Steps in HDFS Architect= ure documentation > -------------------------------------------------------------------------= ----------------- > > Key: HDFS-12827 > URL: https://issues.apache.org/jira/browse/HDFS-12827 > Project: Hadoop HDFS > Issue Type: Improvement > Components: documentation > Reporter: Suri babu Nuthalapati > Priority: Minor > > The placement should be this:=20 > https://hadoop.apache.org/docs/r1.2.1/hdfs_design.html > HDFS=E2=80=99s placement policy is to put one replica on one node in the = local rack, another on a node in a different (remote) rack, and the last on= a different node in the same remote rack. > Hadoop Definitive guide says the same and I have tested and saw the same = behavior as above. > ############ > But the documentation in the versions after r2.5.2 it was mentioned as: > http://hadoop.apache.org/docs/r2.5.2/hadoop-project-dist/hadoop-hdfs/Hdfs= Design.html > HDFS=E2=80=99s placement policy is to put one replica on one node in the = local rack, another on a different node in the local rack, and the last on = a different node in a different rack.=20 -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org