Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 9308FEA75 for ; Mon, 11 Feb 2013 02:12:34 +0000 (UTC) Received: (qmail 62491 invoked by uid 500); 11 Feb 2013 02:12:29 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 62389 invoked by uid 500); 11 Feb 2013 02:12:29 -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 62382 invoked by uid 99); 11 Feb 2013 02:12:29 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 02:12:29 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of michael@cloudera.com designates 74.125.82.46 as permitted sender) Received: from [74.125.82.46] (HELO mail-wg0-f46.google.com) (74.125.82.46) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 02:12:23 +0000 Received: by mail-wg0-f46.google.com with SMTP id fg15so4277311wgb.1 for ; Sun, 10 Feb 2013 18:12:03 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:from:in-reply-to:mime-version:date:message-id :subject:to:content-type:x-gm-message-state; bh=SwWpKZMtgqSm9yn+vnoDbt3zs/dKI8DMy05ZM9Hw4qo=; b=ik84oKfXKbf5QCUWMxTGl6RX4DOxAFl+38PueMzCfNYGI3l9X8RBYdH7IzfqOj4XJI BfHuaElVrB1sVEZg7+Sfbjzte9LWiXoqR4CX7+r6RNrTVjQfTa1lkBm4jn/KmApxIRVJ SA30wgfRijF4b7DIXVuMSMHZD5cg/ulgof0axbzn6XvI8pmRYqDK5YXsb+Bag29Akc2u kZUEkaqZx4zMKYJpiwUfHiCzgon3PVrB8FaNVblWwhXyiUAtOa/X4FDbNuWejq3TlnBA RHTdGa6TA9tA4K8xqmDl9QxqMsA3yfygd4QgVt70Y3J9uJtp+werEvBuC3LCVmQ/FrHF h4Zw== X-Received: by 10.194.238.226 with SMTP id vn2mr20850560wjc.23.1360548723102; Sun, 10 Feb 2013 18:12:03 -0800 (PST) References: From: Michael Katzenellenbogen In-Reply-To: Mime-Version: 1.0 (1.0) Date: Sun, 10 Feb 2013 21:12:02 -0500 Message-ID: <2907752921904630981@unknownmsgid> Subject: Re: Mutiple dfs.data.dir vs RAID0 To: "user@hadoop.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQloTK+tWxuVAWw05x6neExxbN27M4op+pDQi0gaCvhFZKjXg0UHbVi9MWR7fnDG8bOSrXfw X-Virus-Checked: Checked by ClamAV on apache.org One thought comes to mind: disk failure. In the event a disk goes bad, then with RAID0, you just lost your entire array. With JBOD, you lost one disk. -Michael On Feb 10, 2013, at 8:58 PM, Jean-Marc Spaggiari wrote: > Hi, > > I have a quick question regarding RAID0 performances vs multiple > dfs.data.dir entries. > > Let's say I have 2 x 2TB drives. > > I can configure them as 2 separate drives mounted on 2 folders and > assignes to hadoop using dfs.data.dir. Or I can mount the 2 drives > with RAID0 and assigned them as a single folder to dfs.data.dir. > > With RAID0, the reads and writes are going to be spread over the 2 > disks. This is significantly increasing the speed. But if I put 2 > entries in dfs.data.dir, hadoop is going to spread over those 2 > directories too, and at the end, ths results should the same, no? > > Any experience/advice/results to share? > > Thanks, > > JM