mapreduce.jobtracker.expire.trackers.interval no effect
Hi, we want to set the heartbeat timout for a tasktracker. If the tasktracker does not send heartbeats for 60 seconds he should be marked as lost. I found the parameter mapreduce.jobtracker.expire.trackers.interval which sounds right to me. I set mapreduce.jobtracker.expire.trackers.interval 6 in the mapred-site.xml on all servers and restarted the jobtracker and all tasktrackers. I started a benchmark "hadoop jar hadoop-examples.jar randomwriter rand" and every tasktracker gets 2 jobs. It is a small test environment. On one tasktracker i stopped the network. On the jobtracker i could see the "Seconds since heartbeat" increasing. But after 60 seconds the tasktracker was still in the overview. Even in the log of the jobtracker I found nothing. After over 600 seconds i found the message org.apache.hadoop.mapred.JobTracker: Lost tracker . And the tasktracker wasn't shown any more on the jobtracker. Isn't this the right setting? Regards Hansi
Aw: mapreduce.jobtracker.expire.trackers.interval no effect
I forget to say that we use Cloudera 2.0.0-mr1-cdh4.2.0 > Gesendet: Dienstag, 03. Dezember 2013 um 17:38 Uhr > Von: "Hansi Klose" > An: user@hadoop.apache.org > Betreff: mapreduce.jobtracker.expire.trackers.interval no effect > > Hi, > > we want to set the heartbeat timout for a tasktracker. > > If the tasktracker does not send heartbeats for 60 seconds he should > be marked as lost. > > I found the parameter mapreduce.jobtracker.expire.trackers.interval > which sounds right to me. > > I set > > > mapreduce.jobtracker.expire.trackers.interval > 6 > > > in the mapred-site.xml on all servers and restarted the jobtracker and all > tasktrackers. > > I started a benchmark "hadoop jar hadoop-examples.jar randomwriter rand" and > every tasktracker gets 2 jobs. > It is a small test environment. > > On one tasktracker i stopped the network. On the jobtracker i could see the > "Seconds since heartbeat" > increasing. But after 60 seconds the tasktracker was still in the overview. > Even in the log of the jobtracker I found nothing. > > After over 600 seconds i found the message > org.apache.hadoop.mapred.JobTracker: Lost tracker . > And the tasktracker wasn't shown any more on the jobtracker. > > Isn't this the right setting? > > Regards Hansi >
Aw: Re: mapreduce.jobtracker.expire.trackers.interval no effect
Hi adam, in our enviroment it does not matter what i insert there it always take over 600 seconds. I tried 3 and the resulte was the same. Regards Hansi Gesendet: Dienstag, 03. Dezember 2013 um 19:23 Uhr Von: "Adam Kawa" An: user@hadoop.apache.org Betreff: Re: mapreduce.jobtracker.expire.trackers.interval no effect I did a small test, and I a setting mapred.tasktracker.expiry.interval=6 worked for me (TT became considered as lost after around 66 seconds). Can the formula be: mapred.tasktracker.expiry.interval + 2 * some-heartbeat-interval-that-is-3-sec-by-default? Otherwise, is the 6 sec some kind of time needed to make a decision to consider TT as lost? 2013/12/3 Hansi Klose I forget to say that we use Cloudera 2.0.0-mr1-cdh4.2.0 > Gesendet: Dienstag, 03. Dezember 2013 um 17:38 Uhr > Von: "Hansi Klose" > An: user@hadoop.apache.org[user@hadoop.apache.org] > Betreff: mapreduce.jobtracker.expire.trackers.interval no effect > > Hi, > > we want to set the heartbeat timout for a tasktracker. > > If the tasktracker does not send heartbeats for 60 seconds he should > be marked as lost. > > I found the parameter mapreduce.jobtracker.expire.trackers.interval > which sounds right to me. > > I set > > > mapreduce.jobtracker.expire.trackers.interval > 6 > > > in the mapred-site.xml on all servers and restarted the jobtracker and all > tasktrackers. > > I started a benchmark "hadoop jar hadoop-examples.jar randomwriter rand" and > every tasktracker gets 2 jobs. > It is a small test environment. > > On one tasktracker i stopped the network. On the jobtracker i could see the > "Seconds since heartbeat" > increasing. But after 60 seconds the tasktracker was still in the overview. > Even in the log of the jobtracker I found nothing. > > After over 600 seconds i found the message > org.apache.hadoop.mapred.JobTracker: Lost tracker . > And the tasktracker wasn't shown any more on the jobtracker. > > Isn't this the right setting? > > Regards Hansi >
Aw: mapreduce.jobtracker.expire.trackers.interval no effect
Hi. i think i found the reason. I looked at the job.xml and found the parameter mapred.tasktracker.expiry.interval 600 and mapreduce.jobtracker.expire.trackers.interval 3 So i tried the deprecated parameter mapred.tasktracker.expiry.interval in my configuration and voila it works! Why they write that the parameter is deprecated when the new one is not working and will be overwritten by the old one with the default value? http://archive.cloudera.com/cdh4/cdh/4/hadoop-2.0.0-cdh4.2.0/hadoop-project-dist/hadoop-common/DeprecatedProperties.html Regards Hansi > Gesendet: Dienstag, 03. Dezember 2013 um 17:38 Uhr > Von: "Hansi Klose" > An: user@hadoop.apache.org > Betreff: mapreduce.jobtracker.expire.trackers.interval no effect > > Hi, > > we want to set the heartbeat timout for a tasktracker. > > If the tasktracker does not send heartbeats for 60 seconds he should > be marked as lost. > > I found the parameter mapreduce.jobtracker.expire.trackers.interval > which sounds right to me. > > I set > > > mapreduce.jobtracker.expire.trackers.interval > 6 > > > in the mapred-site.xml on all servers and restarted the jobtracker and all > tasktrackers. > > I started a benchmark "hadoop jar hadoop-examples.jar randomwriter rand" and > every tasktracker gets 2 jobs. > It is a small test environment. > > On one tasktracker i stopped the network. On the jobtracker i could see the > "Seconds since heartbeat" > increasing. But after 60 seconds the tasktracker was still in the overview. > Even in the log of the jobtracker I found nothing. > > After over 600 seconds i found the message > org.apache.hadoop.mapred.JobTracker: Lost tracker . > And the tasktracker wasn't shown any more on the jobtracker. > > Isn't this the right setting? > > Regards Hansi >
unsubscribe
CDH5 MRV1 HA / YARN HA port assignment
Hi, I am playing with CDH5 jobtracker HA and YARN HA configuration. I am wondering about the configuration example in their web site. http://www.cloudera.com/content/cloudera-content/cloudera-docs/CDH5/latest/CDH5-High-Availability-Guide/cdh5hag_jt_ha_config.html They uses for each service on different nodes different ports. Like mapred.jobtracker.rpc-address.logicaljt.jt1 = myjt1.myco.com:8021 mapred.jobtracker.rpc-address.logicaljt.jt2 = myjt2.myco.com:8022 mapred.job.tracker.http.address.logicaljt.jt1 = 0.0.0.0:50030 mapred.job.tracker.http.address.logicaljt.jt2 = 0.0.0.0:50031 mapred.ha.jobtracker.rpc-address.logicaljt.jt1 = myjt1.myco.com:8023 mapred.ha.jobtracker.rpc-address.logicaljt.jt2 = myjt2.myco.com:8024 mapred.ha.jobtracker.http-redirect-address.logicaljt.jt1 = myjt1.myco.com:50030 mapred.ha.jobtracker.http-redirect-address.logicaljt.jt2 = myjt2.myco.com:50031 Why do I need different ports when i use different nodes? On their web site about YARN HA they write >> "In an HA setting, you should configure two RMs to use different ports (for >> example, ports on different hosts)." But in the example they use the same ports for the 2 ressource managers. So do I need to use different ports on different nodes? Regards Hansi
