-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/15/2013 09:50 AM, Alaric Snell-Pym wrote:

> So, clearly, in Kerberos mode, more than just fs.default.name goes into
> the socket address that the namenode tries to create, right? However,
> I've noticed that by changing dfs.http.address I can make the error
> message vary; with its current value (my.host.name:50070) it produces
> the above error, but if I change it to "localhost" I instead get a
> complain that "localhost:localhost:0" does not contain a valid host_port
> authority instead of "0.0.0.0:0.0.0.0:0".
>
> Can anybody give me some pointers as to where I might be going wrong?

I've been digging into the source code (this is on Hadoop 1.0.4, by the
way; as usual, I forgot to mention that in the original posting, sorry).

This looks interesting:

 if (certSSL || useKrb) {
        boolean needClientAuth =
    conf.getBoolean("dfs.https.need.client.auth", false);
       InetSocketAddress secInfoSocAddr =
    NetUtils.createSocketAddr(infoHost + ":"+ conf.get(
                                "dfs.https.port", infoHost + ":" + 0));
[...]

As far as I can see, that's creating the socket address by taking
infoHost plus a colon, then trying to look up "dfs.https.port" in the
configuration; and if it's not present, falling back to infoHost + ":" +
0, but still prepending infoHost + ":" on the front of it - and thus
creating the invalid "localhost:localhost:0" or "0.0.0.0:0.0.0.0:0" I
see above. I presume this is a BUG!

So, I jubilantly defined "dfs.https.port" in my hdfs-site.conf, thinking
this would cause it to stop using the invalid default, but it seems to
not change a thing!

I can't find equivalent code in Hadoop 2.0.4 (even after figuring out
the way the paths have all changed around thanks to Mavenising the
project!), so I'm presuming the invalid-default bug has been fixed; but
I'm confused as to why I can't work around it on 1.0.4 by just setting
"dfs.https.port"?

ABS

- --
Alaric Snell-Pym
http://www.snell-pym.org.uk/alaric/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJRk2IMAAoJENVnbn/DjbpJLpkP/jDjlbiSzUyvpvxP9qsROKve
z9tC9Rc5vNOWVf/e3yA9rjgqJcojH7pzaFPQ4rAbEQHw0ZrqiOO/NjEoVn/SwGcq
cV9JYeXK/lqlNcoCK14YbIzqHocQ8aKK07lWXbHKmkup84wVXjZbDTWNQHDtaF+V
zRN4sKNIiWJ+221yVeRSM292vL70FWMKjYHdRLmi6OBc1cZ29zhCgkihh4lDo0Ja
5gbQaPbgJebd0N81PIYBF0pmJfHAk1yqPYYOYkuA/8ohY36Qr92a9dAiqk7dfJeG
mNbjAsWkPrs+gk7900sOWjYxzkCRBIbOiKwms6YTaUBPPelTqWBrvC2FoMtMgrlm
i1LxMM07UAqo8v5cIdrOiChrNa2wGTz1kvm5X10Fwzhu2JwVR7ck73uraQ84OcAl
mPfBf8gWVoPwwwHToOSRD2R/MeV0kjIxy9C1yBHenDW3hWRJtK3ZNlwRyMQLe+Cb
G9s1kFqvOj9QjJKChKk54SeHYrTKMddExqvl2Qux6WtMAV2BgpsH+q/V41V6ULKW
p6/FzB1XYHR2AdwTcvmv9oeYvbHM3MpWx+H7z+RnlWjuYCJul/vWHOEE5ltySYa/
+91+0Se3iaVZg6gGjQJN7RRhDjL3up9UyfY587W70GlIyyxRMBkhV2aFfm5M8T5C
v4y38SvK0cD8/6WZ4SBj
=062+
-----END PGP SIGNATURE-----

Reply via email to