hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mohmmadanis moulavi <anis_moul...@yahoo.co.in>
Subject Re: how to start tasktracker only on single port
Date Mon, 14 Nov 2011 13:38:38 GMT
@harsh J
I got it frm Wel Wu,
It can be done using "mapred.task.tracker.report.address" parameter.
Thanks for your reply

From: Harsh J &lt;harsh@cloudera.com&gt;
To: common-user@hadoop.apache.org
Sent: Monday, 14 November 2011 2:00 PM
Subject: Re: how to start tasktracker only on single port

If you are requiring this for monitoring purposes, do notice that the older TaskTracker would
be with a different ID (port number will differ). You can differentiate based on that.

TaskTrackers are mere clients to the JobTracker and hence JobTracker maintains no complete
state of them, like is done on the HDFS side -- neither do TaskTrackers hold state.

Thus, older TaskTrackers may continue to be in the live node list until they time out (10
mins or so usually, configurable). Cause from the JobTracker perspective, new TaskTrackers
are new instances, not replacements. Older instances are cleaned away after they time out.

On 14-Nov-2011, at 1:09 PM, mohmmadanis moulavi wrote:

&gt; Hello,
&gt; Friends I am using Hadoop 0.20.2 version,
&gt; My problem is whenever I kill the tasktracker and start it again, jobtrakcer shows
one extra tasktracker (the one which is killed &amp; the other which has started afterwords)
&gt; I want to do it like this,
&gt; Whenever I kill the tasktracker it will stop sending the heartbeats, but when I again
start tasktracker, It should start again sendingĀ  heartbeats, i.e it should start that tasktrakcer
on same port as that of before,
&gt; what changes should I made in configuration parameters for that, please let me know
&gt; Thanks &amp; Regads,
&gt; Mohmmadanis Moulavi
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message