Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A4809DC78 for ; Thu, 13 Sep 2012 09:16:08 +0000 (UTC) Received: (qmail 9999 invoked by uid 500); 13 Sep 2012 09:16:03 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 9605 invoked by uid 500); 13 Sep 2012 09:16:03 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 9581 invoked by uid 99); 13 Sep 2012 09:16:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2012 09:16:03 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FSL_RCVD_USER,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-ob0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2012 09:15:57 +0000 Received: by obbtb18 with SMTP id tb18so5342396obb.35 for ; Thu, 13 Sep 2012 02:15:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=93sBPaTVDKJIFKz2IFnidvqWLRYa95B2udiqDihE0h8=; b=J7cTJuAcO74iIzNry96PTeydK+ztUripiel6TVVj78OD2vSLrQu8f/hcinhTwS/81n LZrXAD39uu6oKfHCqpW+wSSUs8acJ7I7i6jOnYGq6Y/+7m1+Rwzw17e6QXgZn6S610Y+ mvnwKJQetv1loZU8cRuhVvQKVk4jTkuE1LVwJuuxSzNYleUEhBSCJJsg27pjESTYlE33 CJcLswvo6T1kDfEXuLlGQqAbU5eJUHjAmE4PwEovITQico2JH2ZOaWsqKY6vyqqEtl61 /H17wY0BpfBmp/C8VAJOGqcr0cU3Dzmfn/sNZc2Mc3Ycbkygs3wk6WD3SLXbF8zJ+DFl C3bQ== Received: by 10.60.13.37 with SMTP id e5mr1181726oec.98.1347527736419; Thu, 13 Sep 2012 02:15:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.11.168 with HTTP; Thu, 13 Sep 2012 02:15:16 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Thu, 13 Sep 2012 14:45:16 +0530 Message-ID: Subject: Re: rack topology data update To: user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmtvfmX5/xIT50r56myoHPtGLAcbHEX7su4pmKg4avgl/cILP0ZuX96DkeBYYbO86/d9ARF Hey Steve, True about the decisions part, that still needs the ugly fixing of re-replication. I think I saw it on a JIRA by Patrick A. that was trying to change the way we did this. But placement is also pluggable in 2.x right? Let me find that JIRA (but yeah, am unsure if it was committed). On Thu, Sep 13, 2012 at 2:40 PM, Steve Loughran wrote: > > > On 13 September 2012 09:03, Harsh J wrote: >> >> >> This should be fixed in one of the 2.x releases, where we also refresh >> the cached values. >> > > Really? Which JIRA? > > I've been making changes to the topology logic so you can do some preflight > checking and dump the topologies, but didn't think a clear and reload was in > there. Some decisions on block placement strategy (flat vs hierarchical) are > made early on, so going from flat to multi-switch is not something I'd > recommend. -- Harsh J