Just noticed looking at the hudson console output on an IPv6 enabled
machine that IPv6 addresses show up:
Stopping IPC Server Responder
[exec] [junit] 2010-04-27 22:55:55,069 INFO ipc.Server
(Server.java:run(453)) - Stopping IPC Server listener on 52991
[exec] [junit] 2010-04-27 22:55:55,069 INFO ipc.Server
(Server.java:run(1395)) - IPC Server handler 2 on 52991: exiting
[exec] [junit] 2010-04-27 22:55:55,069 INFO ipc.Server
(Server.java:run(1395)) - IPC Server handler 1 on 52991: exiting
[exec] [junit] 2010-04-27 22:55:55,070 DEBUG ipc.Server
(Server.java:doRead(535)) - IPC Server listener on 52991: disconnecting
client 127.0.1.1:34085. Number of active connections: 1
[exec] [junit] 2010-04-27 22:55:55,070 DEBUG ipc.Client
(Client.java:close(728)) - IPC Client (47) connection to
/0:0:0:0:0:0:0:0:52991 from hudson: closed
[exec] [junit] 2010-04-27 22:55:55,072 DEBUG ipc.Client
(Client.java:run(605)) - IPC Client (47) connection to
/0:0:0:0:0:0:0:0:52991 from hudson: stopped, remaining connections 0
[exec] [junit] 2010-04-27 22:55:55,172 INFO ipc.Server
(Server.java:run(316)) - Starting SocketReader
[exec] [junit] 2010-04-27 22:55:55,172 INFO
metrics.RpcMetrics (RpcMetrics.java:<init>(61)) - Initializing RPC
Metrics with hostName=TestSaslRPC$TestSaslImpl, port=37737
[exec] [junit] 2010-04-27 22:55:55,173 INFO
metrics.RpcDetailedMetrics (RpcDetailedMetrics.java:<init>(55)) -
Initializing RPC Metrics with hostName=TestSaslRPC$TestSaslImpl, port=37737
[exec] [junit] 2010-04-27 22:55:55,175 INFO ipc.Server
(Server.java:run(586)) - IPC Server Responder: starting
[exec] [junit] 2010-04-27 22:55:55,175 INFO ipc.Server
(Server.java:run(1320)) - IPC Server handler 3 on 37737: starting
[exec] [junit] 2010-04-27 22:55:55,175 INFO ipc.Server
(Server.java:run(1320)) - IPC Server handler 2 on 37737: starting
[exec] [junit] 2010-04-27 22:55:55,175 INFO ipc.Server
(Server.java:run(1320)) - IPC Server handler 1 on 37737: starting
[exec] [junit] 2010-04-27 22:55:55,175 INFO ipc.Server
(Server.java:run(1320)) - IPC Server handler 0 on 37737: starting
[exec] [junit] 2010-04-27 22:55:55,175 INFO ipc.Server
(Server.java:run(421)) - IPC Server listener on 37737: starting
[exec] [junit] 2010-04-27 22:55:55,175 INFO ipc.TestSaslRPC
(TestSaslRPC.java:doDigestRpc(227)) - Service IP address for token is
0:0:0:0:0:0:0:0:37737
Later on:
[exec] [junit] 2010-04-27 22:56:25,030 INFO
security.TestDoAsEffectiveUser
(TestDoAsEffectiveUser.java:configureSuperUserIPAddresses(84)) - Local
Ip addresses:
fe80:0:0:0:223:8bff:fe8a:6e3f%2,67.195.138.32,0:0:0:0:0:0:0:1%1,127.0.0.1,127.0.1.1,h1.grid.sp2.yahoo.net
[exec] [junit] 2010-04-27 22:56:25,056 INFO ipc.Server
(Server.java:run(316)) - Starting SocketReader
I just want to check: is this intentional. Has Hadoop and the underlying
libraries (avro, jetty) embraced IPv6, or is this an accidental mixing
of the two stacks on a machine where someone hasn't turned IPv6 off?
If we have embraced IPv6, that has implications for
https://issues.apache.org/jira/browse/HADOOP-3619 : DNS.getHosts
triggers an ArrayIndexOutOfBoundsException in reverseDNS if one of the
interfaces is IPv6
https://issues.apache.org/jira/browse/HADOOP-6056 : Use
java.net.preferIPv4Stack to force IPv4
https://issues.apache.org/jira/browse/HADOOP-3426 : Datanode does not
start up if the local machines DNS isnt working right and
dfs.datanode.dns.interface==default
...etc/
If it's accidental. HADOOP-6056 can make the problem go away.
