hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Created: (MAPREDUCE-958) TT should bail out early when mapred.job.tracker is bound to 0:0:0:0
Date Mon, 07 Sep 2009 15:06:57 GMT
TT should bail out early when mapred.job.tracker is bound to 0:0:0:0
--------------------------------------------------------------------

                 Key: MAPREDUCE-958
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-958
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: tasktracker
    Affects Versions: 0.21.0
            Reporter: Steve Loughran


It's OK for your job tracker's config to tells the JobTracker to come up on port 0:0:0:0,
but its not OK for the TaskTrackers to get the same mapred.job.tracker configuration value,
as it stops the TT from being able to report its heartbeat.

This misconfiguration surfaces in the TT's {{offerService()}} routine catching and logging
a ConnectionRefused exception every time it tries to heartbeat. Now we have improved the error
message in such a situation, it is still a bit late in the process to encounter a problem
which should be obvious the moment the TT looks at its configuration.


Better to have the TT refuse to start up if {{jobTrackAddr.getAddress().isAnyLocalAddress()}}.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message