hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "genericqa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-8232) RMContainer lost queue name when RM HA happens
Date Mon, 30 Apr 2018 06:02:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458337#comment-16458337
] 

genericqa commented on YARN-8232:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  7s{color} | {color:red}
YARN-8232 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | YARN-8232 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12921118/YARN_8232.patch
|
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/20530/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> RMContainer lost queue name when RM HA happens
> ----------------------------------------------
>
>                 Key: YARN-8232
>                 URL: https://issues.apache.org/jira/browse/YARN-8232
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.8.3
>            Reporter: Hu Ziqian
>            Assignee: Hu Ziqian
>            Priority: Major
>         Attachments: YARN_8232.patch
>
>
> RMContainer has a member variable queuename to store which queue the container belongs
to. When RM HA happens and RMContainers are recovered by scheduler based on NM reports, the
queue name isn't recovered and always be null.
> This situation causes some problems. Here is a case in preemption. Preemption uses container's
queue name to deduct preemptable resources when we use more than one preempt selector, (for
example, enable intra-queue preemption,) . The detail is in
> {code:java}
> CapacitySchedulerPreemptionUtils.deductPreemptableResourcesBasedSelectedCandidates(){code}
> If the contain's queue name is null, this function will throw a YarnRuntimeException
because it tries to get the container's TempQueuePerPartition and the preemption fails.
> Our patch solved this problem by setting container queue name when recover containers.
The patch is based on branch-2.8.3.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message