[#SFOS-1163] Hadoop datanode live address coming up with ipv6 address

SmartFrog

Hadoop datanode live address coming up with ipv6 address

Created: 25/Mar/09 11:28 AM (GMT) Updated: 04/Sep/09 01:47 PM (BST)

Component/s:

_service_hadoop

Affects Version/s:

3.17.010

Fix Version/s:

3.17.014

Time Tracking:

Not Specified

Environment:

ubuntu laptop

Issue Links:

Metabug

This issue is covered under:

~~SFOS-1182~~ SF is trying to deploy over IPv6, when it shouldn't

Compatibility:

unknown

Description

« Hide

* Attribute: live.dfs.datanode.address
* Tags: []
* Value:
"http://0:0:0:0:0:0:0:0:8042/"
* Value resolved:
"http://0:0:0:0:0:0:0:0:8042/"

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Steve Loughran added a comment - 25/Mar/09 11:32 AM (GMT)

looks like this is happening deep inside hadoop. workaround: turn off IPV6 as documented
http://www.ubuntugeek.com/how-to-disable-ipv6-in-ubuntu.html

-could have a component that detects ipv6 and fails if it is live.

[ Permlink | « Hide ]

Steve Loughran added a comment - 14/May/09 07:16 PM (BST)

we could catch this when the service goes live: look for IPv6 addresses and fail the deployment.

[ Permlink | « Hide ]

Steve Loughran added a comment - 23/May/09 10:47 AM (BST)

ubuntu 9.04 doesnt let you turn off ipv6, so w need to identify the root cause in hadoop and fix it. It could just be that jetty is listening on ipv4, but the info isnt being picked up

[ Permlink | « Hide ]

Steve Loughran added a comment - 18/Jun/09 04:49 PM (BST)

the solution is to insert the following option into setSFEnvVariables.sh

#IPv4 only, please
export SF_OPTS="-Djava.net.preferIPv4Stack=true"

and in build.properties (for testing)
daemon.jvmargs="-Djava.net.preferIPv4Stack=true"

this switches SF to IPv4 only.