You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-user@hadoop.apache.org by mohmmadanis moulavi <an...@yahoo.co.in> on 2011/11/14 08:39:10 UTC

how to start tasktracker only on single port

Hello,



Friends I am using Hadoop 0.20.2 version,
My problem is whenever I kill the tasktracker and start it again, jobtrakcer shows one extra tasktracker (the one which is killed & the other which has started afterwords)
I want to do it like this,
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,
what changes should I made in configuration parameters for that, please let me know it


Thanks & Regads,
Mohmmadanis Moulavi

Re: how to start tasktracker only on single port

Posted by mohmmadanis moulavi <an...@yahoo.co.in>.
yeah, I mean kill as stop tasktracker.



----- Original Message -----
From: Alexander C.H. Lorenz <wg...@googlemail.com>
To: common-user@hadoop.apache.org; mohmmadanis moulavi <an...@yahoo.co.in>
Cc: 
Sent: Monday, 14 November 2011 1:16 PM
Subject: Re: how to start tasktracker only on single port

Hi,

please explain the reason to kill (I assume kill -9) a tasktracker. The
best way is to use the start / stop scripts.

best,
Alex

On Mon, Nov 14, 2011 at 8:39 AM, mohmmadanis moulavi <
anis_moulavi@yahoo.co.in> wrote:

> Hello,
>
>
>
> Friends I am using Hadoop 0.20.2 version,
> My problem is whenever I kill the tasktracker and start it again,
> jobtrakcer shows one extra tasktracker (the one which is killed & the other
> which has started afterwords)
> I want to do it like this,
> 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,
> what changes should I made in configuration parameters for that, please
> let me know it
>
>
> Thanks & Regads,
> Mohmmadanis Moulavi
>
>


-- 
Alexander Lorenz
http://mapredit.blogspot.com

*P **Think of the environment: please don't print this email unless you
really need to.*

Re: how to start tasktracker only on single port

Posted by "Alexander C.H. Lorenz" <wg...@googlemail.com>.
Hi,

please explain the reason to kill (I assume kill -9) a tasktracker. The
best way is to use the start / stop scripts.

best,
 Alex

On Mon, Nov 14, 2011 at 8:39 AM, mohmmadanis moulavi <
anis_moulavi@yahoo.co.in> wrote:

> Hello,
>
>
>
> Friends I am using Hadoop 0.20.2 version,
> My problem is whenever I kill the tasktracker and start it again,
> jobtrakcer shows one extra tasktracker (the one which is killed & the other
> which has started afterwords)
> I want to do it like this,
> 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,
> what changes should I made in configuration parameters for that, please
> let me know it
>
>
> Thanks & Regads,
> Mohmmadanis Moulavi
>
>


-- 
Alexander Lorenz
http://mapredit.blogspot.com

*P **Think of the environment: please don't print this email unless you
really need to.*

Re: how to start tasktracker only on single port

Posted by Wei Wu <wu...@gmail.com>.
It seems you are looking for
the parameter "mapred.task.tracker.report.address". Set to a fixed port
number 127.0.0.1:50050 (for example) and try it.

Wei

On Mon, Nov 14, 2011 at 3:39 PM, mohmmadanis moulavi <
anis_moulavi@yahoo.co.in> wrote:

> Hello,
>
>
>
> Friends I am using Hadoop 0.20.2 version,
> My problem is whenever I kill the tasktracker and start it again,
> jobtrakcer shows one extra tasktracker (the one which is killed & the other
> which has started afterwords)
> I want to do it like this,
> 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,
> what changes should I made in configuration parameters for that, please
> let me know it
>
>
> Thanks & Regads,
> Mohmmadanis Moulavi
>
>

Re: how to start tasktracker only on single port

Posted by mohmmadanis moulavi <an...@yahoo.co.in>.
@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; 
&gt; 
&gt; 
&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 it
&gt; 
&gt; 
&gt; Thanks &amp; Regads,
&gt; Mohmmadanis Moulavi
&gt;

Re: how to start tasktracker only on single port

Posted by Harsh J <ha...@cloudera.com>.
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:

> Hello,
> 
> 
> 
> Friends I am using Hadoop 0.20.2 version,
> My problem is whenever I kill the tasktracker and start it again, jobtrakcer shows one extra tasktracker (the one which is killed & the other which has started afterwords)
> I want to do it like this,
> 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,
> what changes should I made in configuration parameters for that, please let me know it
> 
> 
> Thanks & Regads,
> Mohmmadanis Moulavi
>