[
https://issues.apache.org/jira/browse/YARN-7079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140521#comment-16140521
]
Wangda Tan commented on YARN-7079:
----------------------------------
[~tianjuan],
Thanks for working on this feature.
I took a very quick scan of uploaded patch. Some questions/comments:
1) As Devaraj said, it's always helpful to have design doc before working on
such a big patch.
2) I found most of the code changes are adding new resource type (range) to the
resource object, which should be based on YARN-3926 for better maintenance. I
haven't clearly considered how to support value range in the new
ResourceInformation object yet, more discussions needed here.
3) Beyond management allocated/available ports in RM, I think we need enforce
in NM as well, correct? Otherwise an app can request port \[1000-1008\], and
once it is launched, it could use more ports than requested.
4) Is it possible that this feature can be replaced by container + special
network settings which we can allocate different IPs to different containers.
With that we don't need to worry about the port management problem at all.
> to support nodemanager ports management
> -----------------------------------------
>
> Key: YARN-7079
> URL: https://issues.apache.org/jira/browse/YARN-7079
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: 田娟娟
> Attachments: YARN_7079.001.patch
>
>
> Just like the vcores and memory, ports is also important resource
> information to job allocation . So we add the ports management logic to yarn.
> It can meet the user jobs' ports request, and never allocate two jobs(with
> same port requirement) to one machine.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
