[
https://issues.apache.org/jira/browse/YARN-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Subru Krishnan updated YARN-3664:
---------------------------------
Attachment: YARN-3664-YARN-2915-v2.patch
[~vvasudev], thanks for your feedback.
Attaching patch (v2) that incorporates your comments. Similar to YARN-5307, the
names is definitely along the lines but are not exactly what you suggested as I
have to tried to align with the final version of YARN-3662 which includes
[~vinodkv]/[~leftnoteasy]'s feedback too.
bq. Can we use something other than ByteBuffer for getParams - this'll become a
problem if you ever expose this information via REST API or wish to update the
object via a REST API(marshalling/unmarshalling ByteBuffer can be painful)
I agree with your observation but we couldn't think of a better alternative
based on the current understanding of the policy space (refer:
YARN-5324/YARN-5325). Also since we have established this is an internal API, I
feel we can revisit once the dust settles on the policies post testing. So I
have left it as ByteBuffer for now.
> Federation PolicyStore internal APIs
> ------------------------------------
>
> Key: YARN-3664
> URL: https://issues.apache.org/jira/browse/YARN-3664
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Subru Krishnan
> Assignee: Subru Krishnan
> Attachments: YARN-3664-YARN-2915-v0.patch,
> YARN-3664-YARN-2915-v1.patch, YARN-3664-YARN-2915-v2.patch
>
>
> The federation Policy Store contains information about the capacity
> allocations made by users, their mapping to sub-clusters and the policies
> that each of the components (Router, AMRMPRoxy, RMs) should enforce
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
