[
https://issues.apache.org/jira/browse/HADOOP-6528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12827994#action_12827994
]
Konstantin Boudnik commented on HADOOP-6528:
--------------------------------------------
This problem has been attacked for the second time in HADOOP-6386 (and follow
up HADOOP-6428).
Now the code which produces it has two workarounds to guarantee that negative
port can't happen _at all_. What happens however - and now we have a clear
indication of it - is a race condition inside of the Jetty server. The port
value is positive inside of {{NameNode.startHttpServer}} but is negative when
{{listener.getLocalPort}} is called from outside of webserver context.
> Jetty returns -1 resulting in Hadoop masters / slaves to fail during startup.
> -----------------------------------------------------------------------------
>
> Key: HADOOP-6528
> URL: https://issues.apache.org/jira/browse/HADOOP-6528
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Hemanth Yamijala
> Attachments: jetty-server-failure.log
>
>
> A recent test failure on Hudson seems to indicate that Jetty's
> Server.getConnectors()[0].getLocalPort() is returning -1 in the
> HttpServer.getPort() method. When this happens, Hadoop masters / slaves that
> use Jetty fail to startup correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
