Return-Path: Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: (qmail 86746 invoked from network); 9 Mar 2011 15:08:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Mar 2011 15:08:44 -0000 Received: (qmail 21092 invoked by uid 500); 9 Mar 2011 15:08:44 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 21043 invoked by uid 500); 9 Mar 2011 15:08:44 -0000 Mailing-List: contact hdfs-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-user@hadoop.apache.org Delivered-To: mailing list hdfs-user@hadoop.apache.org Received: (qmail 21035 invoked by uid 99); 9 Mar 2011 15:08:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Mar 2011 15:08:44 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tobias.schlottke@gmail.com designates 209.85.214.48 as permitted sender) Received: from [209.85.214.48] (HELO mail-bw0-f48.google.com) (209.85.214.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Mar 2011 15:08:35 +0000 Received: by bwz8 with SMTP id 8so1092928bwz.35 for ; Wed, 09 Mar 2011 07:08:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:content-type:content-transfer-encoding :subject:date:message-id:to:mime-version:x-mailer; bh=2K5U4skpOscctzVqjORaj+YZ1UXMPM/ICBED7MqRLIo=; b=hmWXFGoDGW+UleZ0/5XpwmUmYMslzsUF8QwPxrR+wR4VZPc8ajUVIMbE3XkmJ7J3kD f6/KSm+Ju0j3eM7/d8d4dT5eNB2+iaOW2ecMGmRl02hB5dXKVT2K49hbXEOzljr0VcB2 T6JJ9Cegu/cf6SjLRUVImohwPggk+iobMwWwY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=XVumTqeSpl4uTkjdQTfr1zo1duHoaCLtvGcig/I1/hepLTZo9OjE6VGRfZzS1O3fql qIeMyGvkaWNyQQLT2twKFX1SYVkBzfoHu1RTi0XF6tF3fuAJkm0OdiW8mIcjsFboALXx LAaoI7v7p6kKYOjBaTSD17OObALu+vazeQiKw= Received: by 10.204.169.130 with SMTP id z2mr1081936bky.137.1299683295241; Wed, 09 Mar 2011 07:08:15 -0800 (PST) Received: from [192.168.0.31] ([85.183.18.35]) by mx.google.com with ESMTPS id t1sm1019014bkx.7.2011.03.09.07.08.13 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Mar 2011 07:08:14 -0800 (PST) From: Tobias Schlottke Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Namenode and metadata backups via NFS Date: Wed, 9 Mar 2011 16:08:12 +0100 Message-Id: <3DA060BD-4454-4B1A-BC8E-92862F0DAA1D@gmail.com> To: hdfs-user@hadoop.apache.org Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) X-Virus-Checked: Checked by ClamAV on apache.org Hi there, We've just set up a Namenode that backups its metadata (as recommended) = on an NFS store. Since this NFS-Mount is not a netapp appliance and can go down anytime, I just checked what happens if it goes down and found the DFS no longer = reacting until it came back. Is there some best practice on how to configure NFS-Server or the = namenode not to lock / ignore a mount thats going down? I'm using CDH beta 2. Best, Tobias=