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 7FB032681 for ; Mon, 25 Apr 2011 15:04:43 +0000 (UTC) Received: (qmail 67762 invoked by uid 500); 25 Apr 2011 15:04:40 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 67699 invoked by uid 500); 25 Apr 2011 15:04:40 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 67691 invoked by uid 99); 25 Apr 2011 15:04:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Apr 2011 15:04:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of guxiaobo1982@gmail.com designates 209.85.218.48 as permitted sender) Received: from [209.85.218.48] (HELO mail-yi0-f48.google.com) (209.85.218.48) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Apr 2011 15:04:32 +0000 Received: by yia28 with SMTP id 28so918912yia.35 for ; Mon, 25 Apr 2011 08:04:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=WWBGcyXDyFv0A4OSKeULphAjSDrIJnAcDE7Z+QPsr30=; b=xiLuqC2PyP4mdE8qUict3B9xBQRT1SFweSXDwJtEUdf+HSRm5lVZLZT32F6mm/r6pO CsadwEh9zrk4hI9whdh+JVetNtGHN3wJJwQz8AS1bMtpAEyfa7rdSrG1Hn/TnbQdEXAh oPrbtrMaRyLHsniCRd8BBbfvqIOpcEBjLtMDE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=pl4iEzAi67fbhtfeMYPiWQus8KFgaV3ngskYh87aBnPVpG6aHJ3gSkt7wBw/rWuCze 1GkeliEXDHkMbDDYbiPS81XBnc/6cuBxs+/VaZtecpcS9VhOR2QScpAALWlV4pcWQn14 qig2Oc7/D8w3VNfL596ZjNEEXXLERINXeh9S4= MIME-Version: 1.0 Received: by 10.151.99.6 with SMTP id b6mr3311131ybm.342.1303743851960; Mon, 25 Apr 2011 08:04:11 -0700 (PDT) Received: by 10.151.43.4 with HTTP; Mon, 25 Apr 2011 08:04:11 -0700 (PDT) Date: Mon, 25 Apr 2011 23:04:11 +0800 Message-ID: Subject: Does it mean that single disk failure causes the whole datanode to fail? From: Xiaobo Gu To: common-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi, I heard from so many people saying we should using JBOD instead of RAID, that is we should format each local disk(used for data storage) into an individual file system and define the mount point in dfs.data.dir. In this kind of configuration, disk failure will cause the coresponding file system fail, can datanode continue running with file systems defined in dfs.data.dir not accessable? If the answer is no, does it mean single disk failure will cause the whole data node to fail? Regards, Xiaobo Gu