Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 46116 invoked from network); 10 Mar 2008 16:17:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Mar 2008 16:17:04 -0000 Received: (qmail 60675 invoked by uid 500); 10 Mar 2008 16:16:52 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 60651 invoked by uid 500); 10 Mar 2008 16:16:52 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 60642 invoked by uid 99); 10 Mar 2008 16:16:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2008 09:16:52 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [216.109.112.28] (HELO mrout2-b.corp.dcn.yahoo.com) (216.109.112.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2008 16:16:01 +0000 Received: from [10.72.112.37] (battlerock-lm.corp.yahoo.com [10.72.112.37]) by mrout2-b.corp.dcn.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id m2AGGCmT022372 for ; Mon, 10 Mar 2008 09:16:12 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:content-type:message-id: content-transfer-encoding:from:subject:date:to:x-mailer; b=FGbWaC6LfPxc+fw+OB5VqLUfZ9QpW/bh9dsjZf+bysY4UIVqlMMRuayB1FWv+qqk Mime-Version: 1.0 (Apple Message framework v753) In-Reply-To: <47D55228.1070803@attributor.com> References: <15943388.post@talk.nabble.com> <15945833.post@talk.nabble.com> <4E45EC6AD219FD47AD1BC06E4EE3845DBBA765@SNV-EXVS09.ds.corp.yahoo.com> <15946094.post@talk.nabble.com> <47D44EFB.5000805@cs.washington.edu> <944750dd0803091847x7c1d2b3dyd9dd8c3c7faf0f8d@mail.gmail.com> <944750dd0803091852g3d3798c2q970f2c459e1ec8d7@mail.gmail.com> <15950796.post@talk.nabble.com> <47D55228.1070803@attributor.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2EE042F1-137D-4FA0-B1BD-C9DB8C2D94B2@yahoo-inc.com> Content-Transfer-Encoding: 7bit From: "Owen O'Malley" Subject: Re: dynamically adding slaves to hadoop cluster Date: Mon, 10 Mar 2008 09:16:10 -0700 To: core-user@hadoop.apache.org X-Mailer: Apple Mail (2.753) X-Virus-Checked: Checked by ClamAV on apache.org On Mar 10, 2008, at 8:22 AM, Jason Venner wrote: > Is there a /proper/ way to bring up the processes on the slave node > so that the master will recognize them at *stop* time? yes, you can setup the pid files by using (directly on the newly added node!): % bin/hadoop-daemon.sh start datanode % bin/hadoop-daemon.sh start tasktracker then the stop-all will know the pid to shut down. It is unfortunate that start-daemon.sh and start-daemons.sh differ only in the "s". start-daemons.sh should probably be start-slave-daemons.sh or something. -- Owen