[
https://issues.apache.org/jira/browse/YARN-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306593#comment-16306593
]
Wangda Tan commented on YARN-7653:
----------------------------------
Thanks [~pgaref] for working on the JIRA, it looks like the newly added logics
only take care of rack cardinality. Please let me know if I missed any
discussions or logic in the patch. Instead of hardcoded for the rack name, I
think we should support generic node group concept. Otherwise, we have to redo
all the changes in the patch to support generic node group.
I just updated the title of the JIRA to better reflect its changes, and I
suggest to change logic to support generic node group cardinality before the
decay of code architecture.
Thoughts?
> Rack cardinality support for AllocationTagsManager
> --------------------------------------------------
>
> Key: YARN-7653
> URL: https://issues.apache.org/jira/browse/YARN-7653
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Panagiotis Garefalakis
> Assignee: Panagiotis Garefalakis
> Fix For: YARN-6592
>
> Attachments: YARN-7653-YARN-6592.001.patch,
> YARN-7653-YARN-6592.002.patch, YARN-7653-YARN-6592.003.patch
>
>
> AllocationTagsManager currently supports node and cluster-wide tag
> cardinality retrieval.
> If we want to support arbitrary node-groups/scopes for our placement
> constraints TagsManager should be extended to provide such functionality.
> As a first step we need to support RACK scope cardinality retrieval (as
> defined in our API).
> i.e. how many "spark" containers are currently running on "RACK-1"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
