Description
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())."
Attachments
Attachments
Issue Links
- supercedes
-
SAMZA-102 SamzaAppMasterService.scala - exception handling onInit() always assume port conflict, very misleading
- Resolved