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-2380) The normalizeRequests method in SchedulerUtils always resets the vCore to 1
Date Fri, 01 May 2015 22:14:07 GMT

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

Hadoop QA commented on YARN-2380:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  14m 28s | Pre-patch trunk compilation is healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any @author tags.
|
| {color:green}+1{color} | tests included |   0m  0s | The patch appears to include 1 new
or modified test files. |
| {color:green}+1{color} | javac |   7m 28s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |   9m 36s | There were no new javadoc warning messages.
|
| {color:green}+1{color} | release audit |   0m 22s | The applied patch does not increase
the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle |   1m 38s | There were no new checkstyle issues. |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that end in whitespace.
|
| {color:green}+1{color} | install |   1m 34s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 32s | The patch built with eclipse:eclipse.
|
| {color:green}+1{color} | findbugs |   2m 37s | The patch does not introduce any new Findbugs
(version 2.0.3) warnings. |
| {color:green}+1{color} | yarn tests |   1m 55s | Tests passed in hadoop-yarn-common. |
| {color:red}-1{color} | yarn tests |  53m 42s | Tests failed in hadoop-yarn-server-resourcemanager.
|
| | |  93m 57s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests | hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacityScheduler
|
|   | hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesApps |
|   | hadoop.yarn.server.resourcemanager.TestContainerResourceUsage |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12661693/YARN-2380.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 3393461 |
| hadoop-yarn-common test log | https://builds.apache.org/job/PreCommit-YARN-Build/7575/artifact/patchprocess/testrun_hadoop-yarn-common.txt
|
| hadoop-yarn-server-resourcemanager test log | https://builds.apache.org/job/PreCommit-YARN-Build/7575/artifact/patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt
|
| Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/7575/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf906.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep
3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output | https://builds.apache.org/job/PreCommit-YARN-Build/7575/console |


This message was automatically generated.

> The normalizeRequests method in SchedulerUtils always resets the vCore to 1
> ---------------------------------------------------------------------------
>
>                 Key: YARN-2380
>                 URL: https://issues.apache.org/jira/browse/YARN-2380
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.4.0
>            Reporter: Jian Fang
>            Assignee: Jian Fang
>            Priority: Critical
>         Attachments: YARN-2380.patch
>
>
> I added some log info to the method normalizeRequest() as follows.
>   public static void normalizeRequest(
>       ResourceRequest ask, 
>       ResourceCalculator resourceCalculator, 
>       Resource clusterResource,
>       Resource minimumResource,
>       Resource maximumResource,
>       Resource incrementResource) {
>     LOG.info("Before request normalization, the ask capacity: " + ask.getCapability());
>     Resource normalized = 
>         Resources.normalize(
>             resourceCalculator, ask.getCapability(), minimumResource,
>             maximumResource, incrementResource);
>     LOG.info("After request normalization, the ask capacity: " + normalized);
>     ask.setCapability(normalized);
>   }
> The resulted log showed that the vcore in ask was changed from 2 to 1.
> 2014-08-01 20:54:15,537 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils
(IPC Server handler 4 on 9024): Before request normalization, the ask capacity: <memory:1536,
vCores:2>
> 2014-08-01 20:54:15,537 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.SchedulerUtils
(IPC Server handler 4 on 9024): After request normalization, the ask capacity: <memory:1536,
vCores:1>
> The root cause is the DefaultResourceCalculator calls Resources.createResource(normalizedMemory)
to regenerate a new resource with vcore = 1.
> This bug is critical and it leads to the mismatch of the request resource and the container
resource and many other potential issues if the user requests containers with vcore > 1.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message