[
https://issues.apache.org/jira/browse/HADOOP-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michele (aka pirroh) Catasta updated HADOOP-6056:
-------------------------------------------------
Attachment: HADOOP-6056.patch.2
Hi Todd,
+1 on the trade-off you suggested. I added HADOOP_ALLOW_IPV6 in the attached
patch.
Should we also let it manage the preferIPv4Stack option? (e.g. if ALLOW, then
preferIPv4stack=false). As of today, it won't be of any benefit.
As a side note, I've no idea how the final merging of the
hadoop-env.sh.template files happens, so I just modified the one in
hadoop-common.
> 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: Michele (aka pirroh) Catasta
> Fix For: 0.21.0, 0.22.0
>
> Attachments: HADOOP-6056.patch, HADOOP-6056.patch.2, 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.
