[
https://issues.apache.org/jira/browse/HADOOP-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523328
]
Hadoop QA commented on HADOOP-1790:
-----------------------------------
+1
http://issues.apache.org/jira/secure/attachment/12364697/HADOOP-1790-0.patch
applied and successfully tested against trunk revision r570270.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/631/testReport/
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/631/console
> hadoop seems not to support multi-homed installations
> -----------------------------------------------------
>
> Key: HADOOP-1790
> URL: https://issues.apache.org/jira/browse/HADOOP-1790
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.14.0
> Reporter: Torsten Curdt
> Priority: Blocker
> Fix For: 0.14.1
>
> Attachments: HADOOP-1790-0.patch, multi-interface.diff
>
>
> The exception is similar to HADOOP-1739 but it seems to be a different reason
> for us. We have a multi homed boxes and have specified the
> mapred.task.tracker.report.bindAddress to be a local 192.x address. The
> tracker process only uses the default constructor to create an
> InetSocketAddress in TaskTracker and misses to connect to the report server
> which is listening on 192.x now.
> The attached patch should solve that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
