hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenji Kikushima (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-500) ResourceManager webapp is using next port if configured port is already in use
Date Mon, 08 Apr 2013 08:19:16 GMT

     [ https://issues.apache.org/jira/browse/YARN-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kenji Kikushima updated YARN-500:
---------------------------------

    Attachment: YARN-500.patch

ResourceManager & NodeManager webapp calls Builder<T> at(String bindAddress) method
in o.a.h.yarn.webapp.WebApps.
This method always enables findPort(private variable).
If findPort enabled and configured port was already in use, webapp try to use next port.
So, I made a patch to disable findPort if configured port was not zero.
This spec is same as NameNode webapp.
                
> ResourceManager webapp is using next port if configured port is already in use
> ------------------------------------------------------------------------------
>
>                 Key: YARN-500
>                 URL: https://issues.apache.org/jira/browse/YARN-500
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.0.2-alpha, 2.0.1-alpha
>            Reporter: Nishan Shetty
>         Attachments: YARN-500.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message