Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6C3F9FFCE for ; Tue, 9 Apr 2013 20:50:00 +0000 (UTC) Received: (qmail 14511 invoked by uid 500); 9 Apr 2013 20:49:55 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 14394 invoked by uid 500); 9 Apr 2013 20:49:55 -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 14385 invoked by uid 99); 9 Apr 2013 20:49:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 20:49:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of athomewithagroovebox@gmail.com designates 74.125.82.169 as permitted sender) Received: from [74.125.82.169] (HELO mail-we0-f169.google.com) (74.125.82.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 20:49:49 +0000 Received: by mail-we0-f169.google.com with SMTP id x43so6014308wey.28 for ; Tue, 09 Apr 2013 13:49:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type; bh=mR+715NrYRt8MsqqVL0uLRqFxQwQETSmKP82vHqK0eU=; b=l6uLH5jpAbIeHWIy4E25O9RGct+vv/mYev1IwqfEh3ATBF3/Nre3A7pYcpqWq4Wxpy QKsVh+flDiW4mwRg4BgopahtIDuqJFQgGlGfOGx0UeeKZC8oah/dM/R59skTSZp1qOmv OxrzyDQoMwq0uI5Du0lWu1V5C2+YABUL7gGP/AlGnKd9SzObvH99zmH80OGLbaTEHivt DOgkJz3jEGNKZupRtaksF7D1V5w/h/rCT9u0yHgeikvOUQI2yaCys9K6ckQjOMGVKkAV G9rjnAPnVA8hnwSnMBmvHjstqmjBLTeCmcwjyCeaJ4dbwYNLZYKD3s7oZP/cJugsez9K Nzyg== X-Received: by 10.180.97.132 with SMTP id ea4mr22202154wib.23.1365540569035; Tue, 09 Apr 2013 13:49:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.192.70 with HTTP; Tue, 9 Apr 2013 13:49:07 -0700 (PDT) From: jeremy p Date: Tue, 9 Apr 2013 13:49:07 -0700 Message-ID: Subject: When copying a file to HDFS, how to control what nodes that file will reside on? To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=f46d04426c4e8b372004d9f3b0c0 X-Virus-Checked: Checked by ClamAV on apache.org --f46d04426c4e8b372004d9f3b0c0 Content-Type: text/plain; charset=ISO-8859-1 Hey all, I'm dealing with kind of a bizarre use case where I need to make sure that File A is local to Machine A, File B is local to Machine B, etc. When copying a file to HDFS, is there a way to control which machines that file will reside on? I know that any given file will be replicated across three machines, but I need to be able to say "File A will DEFINITELY exist on Machine A". I don't really care about the other two machines -- they could be any machines on my cluster. Thank you. --f46d04426c4e8b372004d9f3b0c0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hey all,

I'm dealing wit= h kind of a bizarre use case where I need to make sure that File A is local= to Machine A, File B is local to Machine B, etc. =A0When copying a file to= HDFS, is there a way to control which machines that file will reside on? = =A0I know that any given file will be replicated across three machines, but= I need to be able to say "File A will DEFINITELY exist on Machine A&q= uot;. =A0I don't really care about the other two machines -- they could= be any machines on my cluster.

Thank you.
--f46d04426c4e8b372004d9f3b0c0--