[
https://issues.apache.org/jira/browse/YARN-8765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613926#comment-16613926
]
Suma Shivaprasad commented on YARN-8765:
----------------------------------------
Thanks [~cheersyang]! for starting this and uploading the design.
It would be useful to add a RANGE resource type to manage resource types like
IPs, ports ..for easier management...since IPs/ports etc are usually
specified/dealt with as a range...
with RANGE, there could either be a value for the range( eg: CIDR range) or a
min/lower bound and max/upperBound. There could be a plugin in RM to validate
the values specified for the resource types. (eg : validate CIDR range).
We may also need to support the case where IP ranges may not be restricted to
individual NM reported IPs and IPs can move across hosts, given the underlying
network model supports it. RM would manage a global routable IP range in this
case and when containers are allocated, RM could assign an available IP from
this range.
Thoughts?
> Extend YARN to support SET type of resources
> --------------------------------------------
>
> Key: YARN-8765
> URL: https://issues.apache.org/jira/browse/YARN-8765
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Weiwei Yang
> Priority: Major
>
> YARN-3926 evolves a new resource model in YARN by providing a general
> resource definition mechanism. However right now only COUNTABLE type is
> supported. To support resources that cannot be declared with a single value,
> propose to add a SET type. This will extend YARN to manage IP address
> resources. Design doc is attached
> [here|https://docs.google.com/document/d/1U9hj1xX9a3c_xT_X4EP_YC0fZ7ItD5X-rB0bYne-waU/edit?usp=sharing].
> This feature is split from YARN-8446.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
