hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michele (aka pirroh) Catasta (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6056) Use java.net.preferIPv4Stack to force IPv4
Date Tue, 19 Jan 2010 12:55:54 GMT

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

Michele (aka pirroh) Catasta updated HADOOP-6056:

    Status: Patch Available  (was: Open)

net.ipv6.bindv6only = 1 is currently breaking Java networking:

To let Hadoop run correctly on Debian Squeeze, I needed both Todd's patch and the workaround
proposed in that bug report.
Attaching a trivial patch that checks the parameter value, and exits gracefully if it's 1.
You can comment out the exit part and leave it as a simple warning, but, given my previous
experience, it would be a waste of time. Daemons take 2min in average to come up, and you
realize something is not working only after launching an example job.

Manually tested on Debian Squeeze and Ubuntu 9.10

> Use java.net.preferIPv4Stack to force IPv4
> ------------------------------------------
>                 Key: HADOOP-6056
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6056
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: scripts
>    Affects Versions: 0.21.0, 0.22.0
>            Reporter: Steve Loughran
>            Assignee: Todd Lipcon
>             Fix For: 0.21.0, 0.22.0
>         Attachments: hadoop-6056.txt
> This was mentioned on HADOOP-3427, there is a property,  java.net.preferIPv4Stack, which
you set to true for the java net process to switch to IPv4 everywhere. 
> As Hadoop doesn't work on IPv6, this should be set to true in the startup scripts. Hopefully
this will ensure that Jetty will also pick it up.

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

View raw message