[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916291#comment-16916291 ] Tao Yang commented on YARN-8917: Thanks [~rohithsharma], [~leftnoteasy], [~sunilg] for the review and commit! > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Critical > Fix For: 3.3.0, 3.2.1 > > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915896#comment-16915896 ] Hudson commented on YARN-8917: -- FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #17184 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/17184/]) YARN-8917. Absolute (maximum) capacity of level3+ queues is wrongly (rohithsharmaks: rev 689d2e61058b5f719c6cbe9897a72b19b44a29a3) * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestAbsoluteResourceConfiguration.java * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/ParentQueue.java > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Critical > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915890#comment-16915890 ] Rohith Sharma K S commented on YARN-8917: - Committing shortly.. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Critical > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915758#comment-16915758 ] Hadoop QA commented on YARN-8917: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 58s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 20m 27s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 40s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 33s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 43s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 12m 46s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 16s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 43s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 41s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 41s{color} | {color:green} the patch passed {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 30s{color} | {color:orange} hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: The patch generated 1 new + 25 unchanged - 0 fixed = 26 total (was 25) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 41s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 12m 51s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 24s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 29s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 87m 3s{color} | {color:green} hadoop-yarn-server-resourcemanager in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 38s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}142m 49s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=19.03.1 Server=19.03.1 Image:yetus/hadoop:bdbca0e53b4 | | JIRA Issue | YARN-8917 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12944836/YARN-8917.002.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux d5fba3c5cae2 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/patchprocess/precommit/personality/provided.sh | | git revision | trunk / d2225c8 | | maven | version: Apache Maven 3.3.9 | | Default Java | 1.8.0_212 | | findbugs | v3.1.0-RC1 | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/24630/artifact/out/diff-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/24630/testReport/ | | Max. process+thread count | 862 (vs. ulimit of 5500) | | modules | C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-res
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915632#comment-16915632 ] Rohith Sharma K S commented on YARN-8917: - Thanks [~Tao Yang].. I will retriger jenkins again to check does jenkins is intermittent or consistently failing. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Critical > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915628#comment-16915628 ] Tao Yang commented on YARN-8917: Hi, [~rohithsharma], I can't reproduce this failure on trunk branch in my local environment, according to the standard output, the assignment which should allocate a container was broke for unknown reason after checking node, debug info is not enough to locate the cause. Moreover, this patch only affect the capacity shown in WebUI or REST results, won't affect the scheduling process. So I think they are not related. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Critical > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915511#comment-16915511 ] Tao Yang commented on YARN-8917: Sorry for this late reply. I will check it shortly. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Critical > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915474#comment-16915474 ] Rohith Sharma K S commented on YARN-8917: - [~Tao Yang] Test case seems to be related as per my knowledge. Can you check once again please? > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Critical > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913925#comment-16913925 ] Rohith Sharma K S commented on YARN-8917: - [~Tao Yang] Can you look at the test failures whether they are related? > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Critical > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913678#comment-16913678 ] Hadoop QA commented on YARN-8917: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 23s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 20m 42s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 44s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 32s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 47s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 12m 9s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 28s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 33s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 48s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 44s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 44s{color} | {color:green} the patch passed {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 27s{color} | {color:orange} hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: The patch generated 1 new + 25 unchanged - 0 fixed = 26 total (was 25) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 46s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 11m 40s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 19s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 28s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red} 82m 11s{color} | {color:red} hadoop-yarn-server-resourcemanager in the patch failed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 29s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}136m 1s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.yarn.server.resourcemanager.scheduler.capacity.TestLeafQueue | \\ \\ || Subsystem || Report/Notes || | Docker | Client=19.03.1 Server=19.03.1 Image:yetus/hadoop:bdbca0e | | JIRA Issue | YARN-8917 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12944836/YARN-8917.002.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux 5d442ed6e760 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/patchprocess/precommit/personality/provided.sh | | git revision | trunk / 28fb4b5 | | maven | version: Apache Maven 3.3.9 | | Default Java | 1.8.0_222 | | findbugs | v3.1.0-RC1 | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/24609/artifact/out/diff-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt | | unit | https://builds.apache.org/job/PreCommit-YARN-Build/24609/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoo
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16913169#comment-16913169 ] Rohith Sharma K S commented on YARN-8917: - I am re-triggering jenkins to see patch still applies. cc:/ [~Tao Yang] [~sunilg] [~leftnoteasy] > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Critical > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian Jira (v8.3.2#803003) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687411#comment-16687411 ] Hadoop QA commented on YARN-8917: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 14s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 18m 18s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 56s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 36s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 46s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 12m 25s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 12s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 30s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 46s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 39s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 39s{color} | {color:green} the patch passed {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 32s{color} | {color:orange} hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: The patch generated 1 new + 26 unchanged - 0 fixed = 27 total (was 26) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 44s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 12m 18s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 19s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red}102m 28s{color} | {color:red} hadoop-yarn-server-resourcemanager in the patch failed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 24s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}154m 29s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f | | JIRA Issue | YARN-8917 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12944836/YARN-8917.002.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux e45d1da8920d 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/patchprocess/precommit/personality/provided.sh | | git revision | trunk / 21ec4bd | | maven | version: Apache Maven 3.3.9 | | Default Java | 1.8.0_181 | | findbugs | v3.1.0-RC1 | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/22540/artifact/out/diff-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt | | unit | https://builds.apache.org/job/PreCommit-YARN-Build/22540/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt | | Test Results | https://builds.apache.org/job/PreCommit-Y
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687070#comment-16687070 ] Hadoop QA commented on YARN-8917: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 15s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 18m 48s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 45s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 37s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 48s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 12m 52s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 14s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 30s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 45s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 38s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 38s{color} | {color:green} the patch passed {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 29s{color} | {color:orange} hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: The patch generated 1 new + 26 unchanged - 0 fixed = 27 total (was 26) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 42s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 12m 27s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 19s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red}104m 39s{color} | {color:red} hadoop-yarn-server-resourcemanager in the patch failed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 29s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}157m 37s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:8f97d6f | | JIRA Issue | YARN-8917 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12944836/YARN-8917.002.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux 718c9a0d28cc 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/patchprocess/precommit/personality/provided.sh | | git revision | trunk / b57cc73 | | maven | version: Apache Maven 3.3.9 | | Default Java | 1.8.0_181 | | findbugs | v3.1.0-RC1 | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/22538/artifact/out/diff-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt | | unit | https://builds.apache.org/job/PreCommit-YARN-Build/22538/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt | | Test Results | https://builds.apache.org/job/PreCommit-Y
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686903#comment-16686903 ] Wangda Tan commented on YARN-8917: -- This JIRA somehow dropped from our radar, retriggering Jenkins job and will get it committed. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Major > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665841#comment-16665841 ] Tao Yang commented on YARN-8917: Thanks [~sunilg] for the review. I can't reproduce these UT failures in TestRMAdminService on my local environment, they seem not related to this patch. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Major > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664611#comment-16664611 ] Sunil Govindan commented on YARN-8917: -- [~Tao Yang] Thank you for the patch. Few test case failure in TestRMAdminService. I am seeing this for first time. But in first glance not related as well. could you please double check. Thank you > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Major > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664570#comment-16664570 ] Tao Yang commented on YARN-8917: Hi, [~sunilg] [~leftnoteasy], v2 patch updated UT to add assert annotations, could you please help to review again? Thanks. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Major > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657720#comment-16657720 ] Hadoop QA commented on YARN-8917: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 19s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 23m 22s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 0s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 48s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m 8s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 13m 25s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 11s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 28s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 44s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 38s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 38s{color} | {color:green} the patch passed {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 32s{color} | {color:orange} hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager: The patch generated 1 new + 26 unchanged - 0 fixed = 27 total (was 26) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 42s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 12m 35s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 21s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red}101m 52s{color} | {color:red} hadoop-yarn-server-resourcemanager in the patch failed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 27s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}160m 13s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation | | | hadoop.yarn.server.resourcemanager.TestRMAdminService | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:4b8c2b1 | | JIRA Issue | YARN-8917 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12944836/YARN-8917.002.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux 62d1a899fb5e 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9 14:43:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/patchprocess/precommit/personality/provided.sh | | git revision | trunk / f069d38 | | maven | version: Apache Maven 3.3.9 | | Default Java | 1.8.0_181 | | findbugs | v3.1.0-RC1 | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/22265/artifact/out/diff-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt | | unit | https://builds.apache.org/job/PreCommit
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657637#comment-16657637 ] Tao Yang commented on YARN-8917: Thanks [~sunilg], [~leftnoteasy] for the review. {quote} cud u pls write a test case to prove the calculation is wrong in level+3 queues. That will help to really see the problem in tests and easy to understand. {quote} This patch tests the calculation for absolute capacity and absolute max capacity for queues of all levels in TestAbsoluteResourceConfiguration#testEffectiveResourceAfterIncreasingClusterResource, this will help to see problem on level 3+ queues if running without the fix. I will update v2 patch to add assert annotations in UT. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Major > Attachments: YARN-8917.001.patch, YARN-8917.002.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16657113#comment-16657113 ] Wangda Tan commented on YARN-8917: -- Nice catch [~Tao Yang]! Fix makes sense to me. [~sunilg], this happens only under the absolute resource configuration code path, when cluster resource changed, percentage-based capacity needs to be updated as well. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Major > Attachments: YARN-8917.001.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656890#comment-16656890 ] Sunil Govindan commented on YARN-8917: -- [~Tao Yang] cud u pls write a test case to prove the calculation is wrong in level+3 queues. That will help to really see the problem in tests and easy to understand. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Major > Attachments: YARN-8917.001.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656884#comment-16656884 ] Hadoop QA commented on YARN-8917: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 15m 28s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 23m 50s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 45s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 40s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 49s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 12m 56s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 17s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 32s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 46s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 42s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 42s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 33s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 43s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 13m 46s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 21s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 28s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red}106m 53s{color} | {color:red} hadoop-yarn-server-resourcemanager in the patch failed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 55s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black}182m 6s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler | | | hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation | \\ \\ || Subsystem || Report/Notes || | Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hadoop:4b8c2b1 | | JIRA Issue | YARN-8917 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12944696/YARN-8917.001.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux 154c839959fd 3.13.0-153-generic #203-Ubuntu SMP Thu Jun 14 08:52:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | /testptch/patchprocess/precommit/personality/provided.sh | | git revision | trunk / 285d2c0 | | maven | version: Apache Maven 3.3.9 | | Default Java | 1.8.0_181 | | findbugs | v3.1.0-RC1 | | unit | https://builds.apache.org/job/PreCommit-YARN-Build/22251/artifact/out/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/22251/testReport/ | | Max. process+thread count | 871 (vs. ulimit of 1) | | modules | C: hadoop-yarn-project/hadoop-y
[jira] [Commented] (YARN-8917) Absolute (maximum) capacity of level3+ queues is wrongly calculated for absolute resource
[ https://issues.apache.org/jira/browse/YARN-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656524#comment-16656524 ] Tao Yang commented on YARN-8917: Attached v1 patch for review. > Absolute (maximum) capacity of level3+ queues is wrongly calculated for > absolute resource > - > > Key: YARN-8917 > URL: https://issues.apache.org/jira/browse/YARN-8917 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Affects Versions: 3.2.1 >Reporter: Tao Yang >Assignee: Tao Yang >Priority: Major > Attachments: YARN-8917.001.patch > > > Absolute capacity should be equal to multiply capacity by parent-queue's > absolute-capacity, > but currently it's calculated as dividing capacity by parent-queue's > absolute-capacity. > Calculation for absolute-maximum-capacity has the same problem. > For example: > root.a capacity=0.4 maximum-capacity=0.8 > root.a.a1 capacity=0.5 maximum-capacity=0.6 > Absolute capacity of root.a.a1 should be 0.2 but is wrongly calculated as 1.25 > Absolute maximum capacity of root.a.a1 should be 0.48 but is wrongly > calculated as 0.75 > Moreover: > {{childQueue.getQueueCapacities().getCapacity()}} should be changed to > {{childQueue.getQueueCapacities().getCapacity(label)}} to avoid getting wrong > capacity from default partition when calculating for a non-default partition. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org