[ https://issues.apache.org/jira/browse/YARN-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897155#comment-15897155 ]
Varun Saxena commented on YARN-6148: ------------------------------------ Me and Naga just had an offline discussion with [~sunilg]. Will update the summary. # We will report a default applicable label for application (if none is specified) which can either be the label in Application Submission context or queue default label, in both Register AM response and in Allocate Response. Latter because application can move across queues. # When the label for a node changes, we will also report this node as part of updated nodes report in Allocate Response. # We would also update Container Info in allocated containers list to include information such as label info including whether its a non exclusive label and the type of container i.e. guaranteed or opportunistic. # At a high level, MR AM will maintain a list of node to label information so as to ascertain which label should the node blacklist be accounted for. Implementation wise, this can probably be done by updating the assigned requests. # When default label for an application changes which will typically happen when application moves across queues, we will consider only the blacklisting failures on target queue's default label to ignore blacklisting. If application moves back and forth across queues, say y => x => y, we can reconstruct the applicable node count for blacklisting as we have both the blacklisted nodes and their mapping to a label. Thoughts? > 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