Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type;
  b=KThyA7Yg5YA9d4KuSIUnHgV0l05phHStn2LrvCVRQP25z71profwwLM1UC6tCvkobrAfEL9gwBF1DtykGJ+POfs+XHl+X3j+6A/Lakp91Su0ck7vyi91QfofUsLvfVjbEWwPOZMlkmroeIHdKANi3Z/Nv46fm8apzdaDRZiqNCE=;
Message-ID: <365982.91127.qm@web112117.mail.gq1.yahoo.com>
Date: Thu, 11 Nov 2010 02:41:52 -0800 (PST)
From: Grandl Robert <rgrandl@yahoo.com>
Subject: Hadoop - stop-dfs.sh, stop-mapred.sh does not stop all instances
To: general@hadoop.apache.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1855586541-1289472112=:91127"

--0-1855586541-1289472112=:91127
Content-Type: text/plain; charset=us-ascii

Hi all,

Probably is a stupid question but I don't figure out what happens.

For example I start on master, start-dfs.sh, start-mapred.sh

However, when I want to stop: stop-mapred, stop-dfs, only one slave instance is killed. 

For example in on the master I am doing something like that:

rgrandl@ikq01:~/hadoop/hadoop-0.21.0$ bin/stop-mapred.sh 
stopping jobtracker
ikq02.rrr: no tasktracker to stop
ikq03.rrr: stopping tasktracker

But I have a tasktracker on ikq02 as well which is not stopped anyway.
rgrandl@ikq02:~$ jps
2462 Jps
2211 TaskTracker
2109 DataNode

Same thing for stop-dfs.sh


Always the tasktracker, datanode instances are killed only on one slave node, even if I have maybe 20 slaves or more. 

Thanks for any clue,
Robert


--0-1855586541-1289472112=:91127--