Return-Path: Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: (qmail 99829 invoked from network); 16 Dec 2010 14:41:52 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Dec 2010 14:41:52 -0000 Received: (qmail 58770 invoked by uid 500); 16 Dec 2010 14:41:52 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 58668 invoked by uid 500); 16 Dec 2010 14:41:50 -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 58660 invoked by uid 99); 16 Dec 2010 14:41:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Dec 2010 14:41:50 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of traviscrawford@gmail.com designates 209.85.213.176 as permitted sender) Received: from [209.85.213.176] (HELO mail-yx0-f176.google.com) (209.85.213.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Dec 2010 14:41:43 +0000 Received: by yxm8 with SMTP id 8so1898096yxm.35 for ; Thu, 16 Dec 2010 06:41:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:references:from:in-reply-to :mime-version:date:message-id:subject:to:content-type; bh=YYlIJ2vy8KSbqxjoxX9ZnsY/ivUcpQ5qRUHdmeEJik8=; b=PWDMEwQht/YJCsV8+V3q5pzwyeC+aJaivnrYQIG6q2CzSXGgVheQ+tHoEvAZZzd46d +gDfOI5GXdEdV4l5jVdDc3F8Yo+aP6aoX4D6eEl/vbqavdbnENIiykvb4mZSxblZGkH+ 2T8R7ZpayUUI5PEk6BPMzmbMBYpGlrvx/tQVY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :content-type; b=Y5JtGdESxDrq5AGS93ZVEMkVDNxVFhKFwYZM+kmPbBJZYYagBBQTpz6BYgwXob1qlT fgQkKdPw6XhpV40pwzLl+dE6Tsh+ebhVIv9zLEaPJdp7a4yL4WyWtGWwozLtd3VUGnMo RK+X4mIQfTEa7JqDB+4ikVgQdZm0K/K4pN49U= Received: by 10.229.222.19 with SMTP id ie19mr1694024qcb.200.1292510482094; Thu, 16 Dec 2010 06:41:22 -0800 (PST) References: <20101216153209.1266e5d3@toffel.linkoping.osa> From: Travis Crawford In-Reply-To: <20101216153209.1266e5d3@toffel.linkoping.osa> Mime-Version: 1.0 (iPad Mail 8C148) Date: Thu, 16 Dec 2010 06:44:26 -0800 Message-ID: <-8889666374499604158@unknownmsgid> Subject: Re: Unbalanced disks - need to take down whole HDFS? To: "hdfs-user@hadoop.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Dec 16, 2010, at 6:34 AM, Erik Forsberg wrote: > Hi! > > I have unbalanced disks on one of my nodes after a disk failure with > disk replacements. > > http://wiki.apache.org/hadoop/FAQ#On_an_individual_data_node.2C_how_do_you_balance_the_blocks_on_the_disk.3F > has a solution, but it starts with "Take down HDFS". > > Is that really necessary - shouldn't taking down just that datanode, > moving around the blocks, then start the datanode be good enough, or > will that mess up some datastructure in the namenode? > You're right - that should say take the DataNode down, move blocks around, then restart the DataNode. You might be able to just replace the disk and have them unbalanced for a while though. As data is created and deleted things will naturally even out. --Travis > Thanks, > \EF > -- > Erik Forsberg > Developer, Opera Software - http://www.opera.com/