[
https://issues.apache.org/jira/browse/YARN-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897069#comment-15897069
]
Sunil G commented on YARN-6209:
-------------------------------
Ideally its better if we get an update from RM regarding the real AM' label.
Let it be coming from ASC or from default label of queue etc. Given that
information in {{RegisterApplicationMasterResponse}}, MR will have idea about
AM containers label. So rather passing as queue;s default label, it could be
passed as AM's label. Now other containers(map/reduce) label are available from
container info rt ?
I agree there are some more grey areas here
# change label of a node at runtime which will impact running containers as
well.
# container launched on a non-exclusive label
If per-label-node-count for requested partition is buffered at RM level, could
we NOT make it dirty when node label s changed in a node. Any way such
containers are prone for preemption when a real ask is available for new label.
As mentioned, I think you are not planning to add this count, correct?
> AM should get notified when application moved to new queue
> ----------------------------------------------------------
>
> Key: YARN-6209
> URL: https://issues.apache.org/jira/browse/YARN-6209
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Rohith Sharma K S
> Assignee: Naganarasimha G R
>
> As Vinod pointed out in
> [comment|https://issues.apache.org/jira/browse/YARN-5068?focusedCommentId=15867356&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15867356],
> when application is moved to different queue, AM should get notified about
> the new queue.
> YARN-1623 adds up queue information in RegisterApplicationMasterResponse.
> The same functionality could be mirrored in AllocateResponse also when app is
> moved to new queue.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
