hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HADOOP-1265) TaskTracker won't bind to localhost
Date Thu, 11 Oct 2007 17:21:51 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Owen O'Malley resolved HADOOP-1265.

       Resolution: Duplicate
    Fix Version/s: 0.15.0

This was fixed by HADOOP-1739, which makes it configurable and defaults the task tracker to

> TaskTracker won't bind to localhost
> -----------------------------------
>                 Key: HADOOP-1265
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1265
>             Project: Hadoop
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.12.3
>         Environment: The firewall looks (something) like this:
> iptables -P INPUT ACCEPT
> iptables -P FORWARD ACCEPT
> iptables -P OUTPUT ACCEPT
> iptables -Z
> # all local connections are OK
> iptables -A INPUT --destination --in-interface lo -j ACCEPT
> iptables -A OUTPUT --destination --out-interface lo -j ACCEPT
> # accept all traffic that originates internally
> iptables -A INPUT --match state --state RELATED,ESTABLISHED -j ACCEPT
> iptables -A OUTPUT --match state --state RELATED,ESTABLISHED -j ACCEPT
> # <snip: open some ports>
> # default target is drop for all unspecified packets
> iptables -P INPUT DROP
> iptables -P FORWARD DROP
> iptables -P OUTPUT DROP
>            Reporter: Eelco Lempsink
>             Fix For: 0.15.0
> Connecting to the TaskTracker with the default configuration fails with the firewall
settings as mentioned in the Environment.  This means the job seems to start, but then will
hang with all tasks at 0%
> Also, setting mapred.tasktracker.dns.interface to 'lo' has no effect.  I would expect
this bound the TaskTracker in such way that local connections would be made.
> To make it work, I have to explicitly poke a hole in the firewall:
> # hadoop
> iptables -A INPUT --protocol tcp --destination-port 50050 -j ACCEPT
> iptables -A OUTPUT --protocol tcp --destination-port 50050 -j ACCEPT
> While in practise a Hadoop will often run on a cluster (so the firewall has to be opened
anyway), I don't think this should be the default behaviour, because it is highly confusing.

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

View raw message