[
https://issues.apache.org/jira/browse/YARN-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898807#comment-15898807
]
Sunil G commented on YARN-6148:
-------------------------------
I generally went through whole approach suggested here, and I still feel there
are some more grey areas.
Could [~varun_saxena] or [~naganarasimha...@apache.org] to put these in a small
doc here. I feel this may be needed because there are small feature sets from
node label / scheduler is playing impact on MR's blacklisting. Few of them are
discussed here, but still its better to brainstorm. To summarize some features
which has impact on blacklist are non-exclusive label, move app, default
queue's label, preemption of non-exclusive label etc.
In hindsight, I feel MR is going to get multiple data sets. Like
per-label-node-count, node-report-on-label-change, app-queue-on-change,
app-default-label-on-change etc in addition to existing MR blacklist. Its
better to get a common consensus here on approach. I thought of looping
[~jlowe] and [~leftnoteasy] as changes are proposed in MR and in YARN's
interface end.
> NM node count reported to AM in Allocate Response should consider requested
> node label partitions.
> --------------------------------------------------------------------------------------------------
>
> Key: YARN-6148
> URL: https://issues.apache.org/jira/browse/YARN-6148
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Varun Saxena
> Assignee: Varun Saxena
> Attachments: YARN-6148.01.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
