Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 42434 invoked from network); 3 Jul 2009 01:34:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Jul 2009 01:34:20 -0000 Received: (qmail 80784 invoked by uid 500); 3 Jul 2009 01:34:28 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 80689 invoked by uid 500); 3 Jul 2009 01:34:28 -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 80679 invoked by uid 99); 3 Jul 2009 01:34:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jul 2009 01:34:28 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [98.136.44.47] (HELO n67.bullet.mail.sp1.yahoo.com) (98.136.44.47) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 03 Jul 2009 01:34:16 +0000 Received: from [216.252.122.216] by n67.bullet.mail.sp1.yahoo.com with NNFMP; 03 Jul 2009 01:33:55 -0000 Received: from [67.195.9.81] by t1.bullet.sp1.yahoo.com with NNFMP; 03 Jul 2009 01:33:55 -0000 Received: from [67.195.9.109] by t1.bullet.mail.gq1.yahoo.com with NNFMP; 03 Jul 2009 01:33:55 -0000 Received: from [127.0.0.1] by omp113.mail.gq1.yahoo.com with NNFMP; 03 Jul 2009 01:33:55 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 217011.83613.bm@omp113.mail.gq1.yahoo.com Received: (qmail 66889 invoked by uid 60001); 3 Jul 2009 01:33:54 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1246584834; bh=UFK58H995UlQOBOXxGul4TTMbbU9n2FuCODxhLEgLAI=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=QtcnD4j+Z7xUFJrrEkEPEIKPkNr/ckNUnqAY1+Wwx5vUIKk0u8oroQ259kgXaahsNxE9z96lhKc/w0C0p3iW3cctbxR9cZIBN9bcEWfxu1cZedPMlJ1b3+Wfz0hmgjSumu3HQ/A1SD2lZ5SqImb3QKhbb7HUScRAG4e8gLtjQuY= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=anEn+aF8CB2x8vhwhvTCACfsHPYnF+rar9qWMevdU7jT47Q/q9wE0IhrGQLmJFoU3S8aiavoS42o9p1Fvkj+NC+ppg+pjFEDlxi8CvzqZYF0aT+TTkZnIdRa+H32EGMzaa9FOLtd4aRhBW2FXlAIueqkfT6RvPuW5dr/ZCCvSLk=; Message-ID: <922183.65481.qm@web111618.mail.gq1.yahoo.com> X-YMail-OSG: L9QjBiUVM1kJZK7jgVgOpV_z5MMQcQgsfO0Hdasjp.gOfHJkbuTdrIg7mkTlj9Apg23VzEizLBX4qEVuE6F6JQZIVS4KQETs4zSF1blp.gmjeoLBvx4L6A4wHPaWdKfqGcyTyHVsLYt10mgyHzopcx.N6zT46gcxoJrOR2biRhzwZbxgPtg58Cwh4KvWSPNhp7.ooulfJEKygwOB4cQx8rHDNogVqYaqD5ndQJ8DJz0TZtV6nPO3.CCFfchalTPctKNUzhfPecEkls8lqaQTyKUK4V5QslzrM_SqB.QUnLidVfLkBQ-- Received: from [198.4.83.52] by web111618.mail.gq1.yahoo.com via HTTP; Thu, 02 Jul 2009 18:33:54 PDT X-Mailer: YahooMailRC/1358.21 YahooMailWebService/0.7.289.15 References: <174375.44189.qm@web111603.mail.gq1.yahoo.com> Date: Thu, 2 Jul 2009 18:33:54 -0700 (PDT) From: Iman E Subject: Re: starting a tasktracker on a specific node in the cluster To: common-user@hadoop.apache.org In-Reply-To: <174375.44189.qm@web111603.mail.gq1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1428242779-1246584834=:65481" X-Virus-Checked: Checked by ClamAV on apache.org --0-1428242779-1246584834=:65481 Content-Type: text/plain; charset=us-ascii The method I described below is now working! The jobtracker takes sometime to update its list of available task trackers (I think it is the timeout of a tasktracker) ________________________________ From: Iman E To: common-user@hadoop.apache.org Sent: Thursday, July 2, 2009 4:18:10 PM Subject: starting a tasktracker on a specific node in the cluster Hi all, I want to start and stop tasktrackers one at a time without using the start-mapred script which also starts the jobtracker. I have tried to do "$HADOOP_CORE_HOME"/bin/hadoop-daemons.sh --config $HADOOP_CONF_DIR --script "$bin"/mapred start tasktracker but the tasktracker starts on the same node as the jobtracker which is not exactly what I want. I expected it to get information about where to start the task tracker from the slaves file. I have also tried to run this on the node where I want the tasktracker to start but it did not work either. Any pointers how to get this running? Thanks Iman --0-1428242779-1246584834=:65481--