You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Zhijie Shen (JIRA)" <ji...@apache.org> on 2015/04/01 05:29:53 UTC

[jira] [Updated] (YARN-3374) Collector's web server should randomly bind an available port

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

Zhijie Shen updated YARN-3374:
------------------------------
    Attachment: YARN-3347.1.patch

With the discovery service, the collector doesn't need to bind a configured port. And in the future, in a single app-level collector mode, we can't configure all collectors on one host to bind the same port. Therefore, I create patch to make the collector randomly bind an available port.  I add a test case to verify a good port is picked randomly. Also, I've verified that the distributed shell is working properly.

> Collector's web server should randomly bind an available port
> -------------------------------------------------------------
>
>                 Key: YARN-3374
>                 URL: https://issues.apache.org/jira/browse/YARN-3374
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>         Attachments: YARN-3347.1.patch
>
>
> It's based on the configuration now. The approach won't work if we move to app-level aggregator container solution. On NM my start multiple such aggregators, which cannot bind to the same configured port.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)