You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/03/07 18:09:46 UTC

[jira] [Created] (SAMZA-175) Bind AM Jetty server to 0

Chris Riccomini created SAMZA-175:
-------------------------------------

             Summary: Bind AM Jetty server to 0
                 Key: SAMZA-175
                 URL: https://issues.apache.org/jira/browse/SAMZA-175
             Project: Samza
          Issue Type: Bug
          Components: yarn
    Affects Versions: 0.6.0
            Reporter: Chris Riccomini


We currently bind YARN's AM Jetty server (both RPC and dashboard) by randomly selecting ports, then retrying if there's a port collision. It looks like Jetty supports fetching of a port after it's been bound (which we need to know, so we can report it to YARN), so we should just bind to 0 instead, and then get the port after the OS selects an open port for Jetty to use.

Documentation here:

http://www.eclipse.org/jetty/documentation/current/configuring-connectors.html

Shows "port: The configured port for the connector or 0 a random available port may be used (selected port available via getLocalPort())."



--
This message was sent by Atlassian JIRA
(v6.2#6252)