[Smartfrog-checkins] [Smartfrog.org-JIRA] Resolved: (SFOS-1274) TT doesnt fail early when it comes up with mapred.job.tracker set to 0:0:0:0

[Steve L. (JIRA) <ji...@sm...>]

     [ http://jira.smartfrog.org/jira/browse/SFOS-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran resolved SFOS-1274.
----------------------------------

    Fix Version/s: 3.17.x
       Resolution: Fixed

checked in the fix -which I've kept in our code. Filed the problem on hadoop as MAPREDUCE-958

> TT doesnt fail early when it comes up with mapred.job.tracker set to 0:0:0:0
> ----------------------------------------------------------------------------
>
>                 Key: SFOS-1274
>                 URL: http://jira.smartfrog.org/jira/browse/SFOS-1274
>             Project: SmartFrog
>          Issue Type: Bug
>          Components: _service_hadoop
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>             Fix For: 3.17.x
>
>
> When the TT comes up, it should look for mapred.job.tracker being bound to 0:0:0:0 -which is what happens when it gets the default jobtracker hostname. By the time the TT comes up, it should be pointed at the real hostname interface. 
> With the single cluster deployments, this worked by waiting for the live.mapred.job.tracker value, but now I'm splitting master and worker, the cluster config needs to be set to the correct value before the master or worker nodes come up. This will have a consequence: the JT will only listen on the single specified address

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira