[
https://issues.apache.org/jira/browse/YARN-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606739#comment-15606739
]
Arun Suresh commented on YARN-5587:
-----------------------------------
I feel we should try to keep this simple. Given that we have already introduced
a {{ProfileCapability}} class that takes a profile name and a possible
Capability override, I propose:
# We create a special {{ProfileCapability}} with profile name *NONE* where user
only specifies the capability (Resource). This would be equivalent to our old
{{Resource}}
# We replace the capability(Resource) argument in both the {{ContainerRequest}}
and {{ResourceRequest}} with {{ProfileCapability}}. Maybe for backward
compatibility, we have 1 constructor that takes Resource and 1 that takes
ProfileCapability. We then convert a Resource to ProfileCapability(NONE,
Resource) in the AMRMClient.
# In the rest of the {{AMRMClient}} codebase, including the
{{RemoteRequestsTable} }we just use {{ProfileCapability}}
> Add support for resource profiles
> ---------------------------------
>
> Key: YARN-5587
> URL: https://issues.apache.org/jira/browse/YARN-5587
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Varun Vasudev
> Assignee: Varun Vasudev
> Attachments: YARN-5587-YARN-3926.001.patch,
> YARN-5587-YARN-3926.002.patch, YARN-5587-YARN-3926.003.patch,
> YARN-5587-YARN-3926.004.patch, YARN-5587-YARN-3926.005.patch
>
>
> Add support for resource profiles on the RM side to allow users to use
> shorthands to specify resource requirements.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
