|
|
-
X not in slaves, yet still being used as a tasktracker
Saptarshi Guha 2009-03-29, 16:00
Hello, A machine X which is the master: it is the jobtracker, namenode and secondary namenode. It is not in the slaves file and is not part of the HDFSHowever in the mapreduce web page, I notice it is being used as a tasktracker. Is the jobtracker always a tasktracker? I'd rather not place too much load on the one machine which plays so many roles. (Hadoop 0.19.0)
Thanks Saptarshi
-
Re: X not in slaves, yet still being used as a tasktracker
Bill Au 2009-03-29, 23:42
The jobtracker does not have to be a tasktracker. Just stop and don't start the tasktracker process. Bill
On Sun, Mar 29, 2009 at 12:00 PM, Saptarshi Guha <[EMAIL PROTECTED]>wrote:
> Hello, > A machine X which is the master: it is the jobtracker, namenode and > secondary namenode. > It is not in the slaves file and is not part of the HDFSHowever in > the mapreduce web page, I notice it is being used as a tasktracker. > Is the jobtracker always a tasktracker? I'd rather not place too much > load on the one machine which plays so many roles. > (Hadoop 0.19.0) > > Thanks > Saptarshi >
-
Re: X not in slaves, yet still being used as a tasktracker
Saptarshi Guha 2009-03-31, 17:51
Aha,there isn't a tasktracker running on X, yet jps shows 4 children and when jobs fail i see failures on X too. So what exactly can I stop? jps output on X 20044 org.apache.hadoop.mapred.JobTracker 12871 org.apache.hadoop.mapred.Child 127.0.0.1 51590 attempt_200903302220_0036_m_000020_0 -541073721 12819 org.apache.hadoop.mapred.Child 127.0.0.1 51590 attempt_200903302220_0036_m_000003_0 1185151254 19768 org.apache.hadoop.hdfs.server.namenode.NameNode 13004 org.apache.hadoop.mapred.Child 127.0.0.1 51590 attempt_200903302220_0036_r_000010_0 1044080068 11396 org.saptarshiguha.rhipe.rhipeserver.RHIPEMain --tsp=mimosa:8200 --listen=4445 --quiet --no-save --max-nsize=1G --max-ppsize=100000 19961 org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode 13131 sun.tools.jps.Jps -ml 22054 12931 org.apache.hadoop.mapred.Child 127.0.0.1 51590 attempt_200903302220_0036_m_000032_0 -690673928 12962 org.apache.hadoop.mapred.Child 127.0.0.1 51590 attempt_200903302220_0036_m_000033_0 203873369
Saptarshi Guha
On Mon, Mar 30, 2009 at 11:37 AM, Saptarshi Guha <[EMAIL PROTECTED]> wrote: > thanks > Saptarshi Guha > > > > On Sun, Mar 29, 2009 at 7:42 PM, Bill Au <[EMAIL PROTECTED]> wrote: >> The jobtracker does not have to be a tasktracker. Just stop and don't start >> the tasktracker process. >> Bill >> >> On Sun, Mar 29, 2009 at 12:00 PM, Saptarshi Guha <[EMAIL PROTECTED]> >> wrote: >>> >>> Hello, >>> A machine X which is the master: it is the jobtracker, namenode and >>> secondary namenode. >>> It is not in the slaves file and is not part of the HDFSHowever in >>> the mapreduce web page, I notice it is being used as a tasktracker. >>> Is the jobtracker always a tasktracker? I'd rather not place too much >>> load on the one machine which plays so many roles. >>> (Hadoop 0.19.0) >>> >>> Thanks >>> Saptarshi >> >> >
|
|