hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5731) Preemption does not work in few corner cases when reservations are placed
Date Wed, 12 Jul 2017 18:59:00 GMT

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

Hadoop QA commented on YARN-5731:
---------------------------------

| (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-5731 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-5731 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12876922/YARN-5731.001.patch
|
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/16391/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Preemption does not work in few corner cases when reservations are placed
> -------------------------------------------------------------------------
>
>                 Key: YARN-5731
>                 URL: https://issues.apache.org/jira/browse/YARN-5731
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler
>    Affects Versions: 2.8.0
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: YARN-5731.001.patch, YARN-5731-branch-2.8.001.patch
>
>
> YARN Capacity Scheduler does not kick Preemption under below scenario.
> Two queues A and B each with 50% capacity and 100% maximum capacity and user limit factor
2. Minimum Container size is 1536MB and total cluster resource is 40GB. Now submit the first
job which needs 1536MB for AM and 9 task containers each 4.5GB to queue A. Job will get 8
containers total (AM 1536MB + 7 * 4.5GB = 33GB) and the cluster usage is 93.8% and the job
has reserved a container of 4.5GB.
> Now when next job (1536MB for AM and 9 task containers each 4.5GB) is submitted onto
queue B. The job hangs in ACCEPTED state forever and RM scheduler never kicks in Preemption.
(RM UI Image 2 attached)
> Test Case:
> ./spark-submit --class org.apache.spark.examples.SparkPi --master yarn-client --queue
A --executor-memory 4G --executor-cores 4 --num-executors 9 ../lib/spark-examples*.jar 1000000
> After a minute..
> ./spark-submit --class org.apache.spark.examples.SparkPi --master yarn-client --queue
B --executor-memory 4G --executor-cores 4 --num-executors 9 ../lib/spark-examples*.jar 1000000
> Credit to: [~Prabhu Joseph] for bug investigation and troubleshooting.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
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