[jira] [Commented] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178611#comment-16178611 ] Sunil G commented on YARN-7105: --- Thanks [~dingda6] for this work. Really appreciate the same. I will helping you in getting this in shape and in comments as well. To start with, let me quote 1st and 2nd points. bq.1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) bq.2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. Here each node is a Queue, and sub-nodes are child queues. And queue usage/configured capacity (not only in percentage, also as absolute values could be needed). So let me add few more additional points as a summary. # Configured vs Used capacity of a queue could be shown as percentage and absolute. # We have a partition, and each queue could have different capacity under each partition. So we could overlay different partitions and its queue capacities in a sequential way like in old RM UI. Or we could select each partition and then visualization of queues will be for that partition. I am not very sure whether point 5 in your list indicating same. # We could add an option to show visualization from a given parent queue. For eg, we have 'sales', 'engg', 'marketing'. So one can also colapse its parents and then view child queues from that point. This could give one department view for any sub-queues. I think you are already planning to handle in point 3. If we could also get an option to hide some parent queues, that also would be really great. Thanks [~dingda6], will wait for your patches to try :) > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png, Screen Shot > 2017-09-24 at 8.50.29 PM.png > > > Based on the discussion with [~wangda], current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > [^Screen Shot 2017-09-24 at 8.19.36 PM.png] > !Screen Shot 2017-09-24 at 8.19.36 PM.png|thumbnail! > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > [^Screen Shot 2017-09-24 at 8.50.29 PM.png] > !Screen Shot 2017-09-24 at 8.50.29 PM.png|thumbnail! > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6509) Add a size threshold beyond which yarn logs will require a force option
[
https://issues.apache.org/jira/browse/YARN-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178571#comment-16178571
]
Hadoop QA commented on YARN-6509:
-
| (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:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
52s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 17m
17s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 12m
11s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
2s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
10s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
53s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
5s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
10s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 5m
47s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 57s{color} | {color:orange} hadoop-yarn-project/hadoop-yarn: The patch
generated 13 new + 123 unchanged - 1 fixed = 136 total (was 124) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 1m
8s{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} findbugs {color} | {color:green} 2m
7s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
3s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
37s{color} | {color:green} hadoop-yarn-common in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 21m 2s{color}
| {color:red} hadoop-yarn-client in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
28s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 81m 11s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.yarn.client.api.impl.TestAMRMClient |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:71bbb86 |
| JIRA Issue | YARN-6509 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12888774/YARN-6509.4.patch |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux 844307674a42 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11
12:48:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / d0b2c58 |
| Default Java | 1.8.0_144 |
| findbugs | v3.1.0-RC1 |
| checkstyle |
https://builds.apache.org/job/PreCommit-YARN-Build/17618/artifact/patchprocess/diff-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
|
| unit |
https://builds.apache.org/job/PreCommit-YARN-Build/17618/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-client.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-YARN-Build/17618/testReport/ |
| modules | C: hadoop-yarn-project/hadoo
[jira] [Commented] (YARN-65) Reduce RM app memory footprint once app has completed
[
https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178548#comment-16178548
]
Rohith Sharma K S commented on YARN-65:
---
+1 lgtm, Failed test cases are known failures! I will commit it later of today
if no more objections
> Reduce RM app memory footprint once app has completed
> -
>
> Key: YARN-65
> URL: https://issues.apache.org/jira/browse/YARN-65
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 0.23.3
>Reporter: Jason Lowe
>Assignee: Manikandan R
> Attachments: YARN-65.001.patch, YARN-65.002.patch, YARN-65.003.patch,
> YARN-65.004.patch, YARN-65.005.patch, YARN-65.006.patch, YARN-65.007.patch,
> YARN-65.008.patch, YARN-65.009.patch, YARN-65.010.patch, YARN-65.011.patch,
> YARN-65.012.patch, YARN-65.013.patch, YARN-65.014.patch, YARN-65.015.patch
>
>
> The ResourceManager holds onto a configurable number of completed
> applications (yarn.resource.max-completed-applications, defaults to 1),
> and the memory footprint of these completed applications can be significant.
> For example, the {{submissionContext}} in RMAppImpl contains references to
> protocolbuffer objects and other items that probably aren't necessary to keep
> around once the application has completed. We could significantly reduce the
> memory footprint of the RM by releasing objects that are no longer necessary
> once an application completes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6509) Add a size threshold beyond which yarn logs will require a force option
[ https://issues.apache.org/jira/browse/YARN-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178527#comment-16178527 ] Xuan Gong commented on YARN-6509: - Thanks for the review, [~djp] Uploaded a new patch to address all of the comments > Add a size threshold beyond which yarn logs will require a force option > --- > > Key: YARN-6509 > URL: https://issues.apache.org/jira/browse/YARN-6509 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Siddharth Seth >Assignee: Xuan Gong > Fix For: 2.9.0 > > Attachments: YARN-6509.1.patch, YARN-6509.2.patch, YARN-6509.3.patch, > YARN-6509.4.patch > > > An accidental fetch for a long running application can lead to scenario which > the large size of log can fill up a disk. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6509) Add a size threshold beyond which yarn logs will require a force option
[ https://issues.apache.org/jira/browse/YARN-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-6509: Attachment: YARN-6509.4.patch > Add a size threshold beyond which yarn logs will require a force option > --- > > Key: YARN-6509 > URL: https://issues.apache.org/jira/browse/YARN-6509 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Siddharth Seth >Assignee: Xuan Gong > Fix For: 2.9.0 > > Attachments: YARN-6509.1.patch, YARN-6509.2.patch, YARN-6509.3.patch, > YARN-6509.4.patch > > > An accidental fetch for a long running application can lead to scenario which > the large size of log can fill up a disk. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Description: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. [^Screen Shot 2017-09-24 at 8.19.36 PM.png] !Screen Shot 2017-09-24 at 8.19.36 PM.png|thumbnail! The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. [^Screen Shot 2017-09-24 at 8.50.29 PM.png] !Screen Shot 2017-09-24 at 8.50.29 PM.png|thumbnail! Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! was: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. !Screen Shot 2017-08-16 at 9.36.13 PM.png|thumbnail! The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png, Screen Shot > 2017-09-24 at 8.50.29 PM.png > > > Based on the discussion with [~wangda], current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > [^Screen Shot 2017-09-24 at 8.19.36 PM.png] > !Screen Shot 2017-09-24 at 8.19.36 PM.png|thumbnail! > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > [^Screen Shot 2017-09-24 at 8.50.29 PM.png] > !Screen Shot 2017-09-24 at 8.50.29 PM.png|thumbnail! > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Description: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. !Screen Shot 2017-08-16 at 9.36.13 PM.png|thumbnail! The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! was: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png, Screen Shot > 2017-09-24 at 8.50.29 PM.png > > > Based on the discussion with [~wangda], current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > !Screen Shot 2017-08-16 at 9.36.13 PM.png|thumbnail! > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Description: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! was: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png, Screen Shot > 2017-09-24 at 8.50.29 PM.png > > > Based on the discussion with [~wangda], current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Description: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! was: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. !Screen Shot 2017-09-24 at 8.50.29 PM.png|thumbnail! Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png, Screen Shot > 2017-09-24 at 8.50.29 PM.png > > > Based on the discussion with [~wangda], current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Description: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. !Screen Shot 2017-09-24 at 8.50.29 PM.png|thumbnail! Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! was: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. !attachment-name.jpg|thumbnail! The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. [^Screen Shot 2017-09-24 at 8.50.29 PM.png] Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png, Screen Shot > 2017-09-24 at 8.50.29 PM.png > > > Based on the discussion with [~wangda], current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > !Screen Shot 2017-09-24 at 8.50.29 PM.png|thumbnail! > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Description: Based on the discussion with [~wangda], current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. !attachment-name.jpg|thumbnail! The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. [^Screen Shot 2017-09-24 at 8.50.29 PM.png] Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! was: Based on the discussion with Wangda Tan, current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. [^Screen Shot 2017-09-24 at 8.19.36 PM.png] The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. [^Screen Shot 2017-09-24 at 8.50.29 PM.png] Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png, Screen Shot > 2017-09-24 at 8.50.29 PM.png > > > Based on the discussion with [~wangda], current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > !attachment-name.jpg|thumbnail! > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > [^Screen Shot 2017-09-24 at 8.50.29 PM.png] > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Description: Based on the discussion with Wangda Tan, current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. [^Screen Shot 2017-09-24 at 8.19.36 PM.png] The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. [^Screen Shot 2017-09-24 at 8.50.29 PM.png] Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! was: Based on the discussion with Wangda Tan, current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png, Screen Shot > 2017-09-24 at 8.50.29 PM.png > > > Based on the discussion with Wangda Tan, current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > [^Screen Shot 2017-09-24 at 8.19.36 PM.png] > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > [^Screen Shot 2017-09-24 at 8.50.29 PM.png] > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Attachment: Screen Shot 2017-09-24 at 8.50.29 PM.png > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png, Screen Shot > 2017-09-24 at 8.50.29 PM.png > > > Based on the discussion with Wangda Tan, current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Description: Based on the discussion with Wangda Tan, current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! was: Based on the discussion with Wangda Tan, current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png > > > Based on the discussion with Wangda Tan, current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Attachment: Screen Shot 2017-09-24 at 8.19.36 PM.png > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > Attachments: Screen Shot 2017-09-24 at 8.19.36 PM.png > > > Based on the discussion with Wangda Tan, current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7105) Refactor of Queue Visualization
[ https://issues.apache.org/jira/browse/YARN-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Da Ding updated YARN-7105: -- Description: Based on the discussion with Wangda Tan, current implementation of Queue is not easy to use if number of nodes is large, and visualization is not very straightforward in terms of node hierarchy and details. Therefore, we want to refactor queue visualization to be more user friendly for different use cases. The image above is the mockup for the new queue visualization, basically it should have the following features: 1. Each node would be visualized by a horizontal bar, and hierarchy would be distinguished by indentation of each node. (e.g. If one node is a child node of another parent node, there would be indentation before the child node.) 2. Each node would show usage info on its bar, e.g. displaying used usage like a progress bar along with the percentage. 3. Click +/- to expand/collapse the tree to show/hide nodes. 4. Click on bar would show detail charts on the bottom. 5. A filter on the top-right would filter the nodes based on options. Currently I finished feature 1 and feature 2. See screenshot. Since this ticket is relatively big and would take a while to complete, I will keep the ticket updated. Don't hesitate to comment your idea or suggestion. Thanks! > Refactor of Queue Visualization > --- > > Key: YARN-7105 > URL: https://issues.apache.org/jira/browse/YARN-7105 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Da Ding >Assignee: Da Ding > > Based on the discussion with Wangda Tan, current implementation of Queue is > not easy to use if number of nodes is large, and visualization is not very > straightforward in terms of node hierarchy and details. Therefore, we want to > refactor queue visualization to be more user friendly for different use cases. > The image above is the mockup for the new queue visualization, basically it > should have the following features: > 1. Each node would be visualized by a horizontal bar, and hierarchy would be > distinguished by indentation of each node. (e.g. If one node is a child node > of another parent node, there would be indentation before the child node.) > 2. Each node would show usage info on its bar, e.g. displaying used usage > like a progress bar along with the percentage. > 3. Click +/- to expand/collapse the tree to show/hide nodes. > 4. Click on bar would show detail charts on the bottom. > 5. A filter on the top-right would filter the nodes based on options. > Currently I finished feature 1 and feature 2. See screenshot. > Since this ticket is relatively big and would take a while to complete, I > will keep the ticket updated. Don't hesitate to comment your idea or > suggestion. Thanks! -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7240) Add more states and transitions to stabilize the NM Container state machine
[
https://issues.apache.org/jira/browse/YARN-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178482#comment-16178482
]
Arun Suresh commented on YARN-7240:
---
Thanks for the patch [~kartheek]. The patch looks mostly good.
Some Comments:
* When we re-queue paused containers (lines 276 - 285 of the
ContainerScheduler) see if we can push the container to the head of the queue
* Remove the "TODO: fix transition" comments from the ContainerImpl
* Since we are introducing a new state "REINITIALIZING_AWAITING_KILL", we need
to update the ContainerImpl::getCurrentState() to map it to RUNNING state.
* Existing tests in {{TestContainerManager}} should be able to verify that the
new "REINITIALIZING_AWAITING_KILL" state works fine, but we should add a test
case to {{TestContainer}}
> Add more states and transitions to stabilize the NM Container state machine
> ---
>
> Key: YARN-7240
> URL: https://issues.apache.org/jira/browse/YARN-7240
> Project: Hadoop YARN
> Issue Type: Improvement
>Reporter: Arun Suresh
>Assignee: kartheek muthyala
> Attachments: YARN-7240.001.patch
>
>
> There seem to be a few intermediate states that can be added to improve the
> stability of the NM container state machine.
> For. eg:
> * The REINITIALIZING should probably be split into REINITIALIZING and
> REINITIALIZING_AWAITING_KILL.
> * Container updates are currently handled in the ContainerScheduler, but it
> would probably be better to have it plumbed through the container state
> machine as a new state, say UPDATING and a new container event.
> The plan is to add some extra tests too to try and test every transition.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6943) Update Yarn to YARN in documentation
[
https://issues.apache.org/jira/browse/YARN-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178463#comment-16178463
]
Sunil G commented on YARN-6943:
---
Thanks [~chetna] for helping in updating this.
One quick comment.
In
{{hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui/src/main/webapp/app/index.html}},
we still use {{YarnUi}} .This could also be {{YARN}}. I think
we need not have to say its Ui again.
> Update Yarn to YARN in documentation
>
>
> Key: YARN-6943
> URL: https://issues.apache.org/jira/browse/YARN-6943
> Project: Hadoop YARN
> Issue Type: Bug
>Reporter: Miklos Szegedi
>Assignee: Chetna Chaudhari
>Priority: Minor
> Labels: newbie
> Attachments: YARN-6943-1.patch, YARN-6943-2.patch, YARN-6943-3.patch
>
>
> Based on the discussion with [~templedf] in YARN-6757 the official case of
> YARN is YARN, not Yarn, so we should update all the md files.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6626) Embed REST API service into RM
[
https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178434#comment-16178434
]
Hadoop QA commented on YARN-6626:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{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:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} yarn-native-services Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 1m
1s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 15m
48s{color} | {color:green} yarn-native-services passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 9m
58s{color} | {color:green} yarn-native-services passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
3s{color} | {color:green} yarn-native-services passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 2m
57s{color} | {color:green} yarn-native-services passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 1m
15s{color} | {color:red} hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api in
yarn-native-services has 1 extant Findbugs warnings. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
37s{color} | {color:green} yarn-native-services passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
14s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 7m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 7m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
10s{color} | {color:green} hadoop-yarn-project/hadoop-yarn: The patch generated
0 new + 246 unchanged - 3 fixed = 246 total (was 249) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 3m
21s{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} xml {color} | {color:green} 0m
5s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
37s{color} | {color:green} hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
generated 0 new + 0 unchanged - 1 fixed = 0 total (was 1) {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
46s{color} | {color:green} hadoop-yarn-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
26s{color} | {color:green} hadoop-yarn-server-resourcemanager in the patch
passed. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
53s{color} | {color:green} hadoop-yarn-services-core in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
40s{color} | {color:green} hadoop-yarn-services-api in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
29s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
46s{color} | {color:green} hadoop-yarn-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
3s{color} | {color:green} hadoop-yarn-common in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 48m 49s{color}
| {color:red} hadoop-yarn-server-resourcemanager in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
17s{color} |
[jira] [Commented] (YARN-6943) Update Yarn to YARN in documentation
[
https://issues.apache.org/jira/browse/YARN-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178426#comment-16178426
]
Hadoop QA commented on YARN-6943:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
18s{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 6 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
23s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 16m
26s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 18m
55s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
35s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 12m
13s{color} | {color:green} trunk passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 12m
9s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 8m
40s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
25s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 11m
38s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 11m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 11m
8s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 2m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 11m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
0s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} shelldocs {color} | {color:green} 0m
13s{color} | {color:green} There were no new shelldocs issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
1s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 12m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 8m
43s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 3m
11s{color} | {color:green} hadoop-kms in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 76m 2s{color}
| {color:red} hadoop-yarn in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
49s{color} | {color:green} hadoop-yarn-api in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
58s{color} | {color:green} hadoop-yarn-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
3s{color} | {color:green} hadoop-yarn-server-common in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
58s{color} | {color:green} hadoop-yarn-registry in the patch passed. {color} |
| {c
[jira] [Comment Edited] (YARN-6626) Embed REST API service into RM
[ https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178396#comment-16178396 ] Eric Yang edited comment on YARN-6626 at 9/24/17 11:11 PM: --- Fixed findbugs and javadoc issues. was (Author: eyang): Fixed findbugs issues. > Embed REST API service into RM > -- > > Key: YARN-6626 > URL: https://issues.apache.org/jira/browse/YARN-6626 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Gour Saha > Fix For: yarn-native-services > > Attachments: YARN-6626.yarn-native-services.001.patch, > YARN-6626.yarn-native-services.002.patch, > YARN-6626.yarn-native-services.003.patch, > YARN-6626.yarn-native-services.004.patch, > YARN-6626.yarn-native-services.005.patch > > > As of now the deployment model of the Native Services REST API service is > standalone. There are several cross-cutting solutions that can be inherited > for free (kerberos, HA, ACLs, trusted proxy support, etc.) by the REST API > service if it is embedded into the RM process. In fact we can expose the REST > API via the same port as RM UI (8088 default). The URI path > /services/v1/applications will distinguish the REST API calls from other RM > APIs. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6626) Embed REST API service into RM
[ https://issues.apache.org/jira/browse/YARN-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Yang updated YARN-6626: Attachment: YARN-6626.yarn-native-services.005.patch Fixed findbugs issues. > Embed REST API service into RM > -- > > Key: YARN-6626 > URL: https://issues.apache.org/jira/browse/YARN-6626 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Gour Saha > Fix For: yarn-native-services > > Attachments: YARN-6626.yarn-native-services.001.patch, > YARN-6626.yarn-native-services.002.patch, > YARN-6626.yarn-native-services.003.patch, > YARN-6626.yarn-native-services.004.patch, > YARN-6626.yarn-native-services.005.patch > > > As of now the deployment model of the Native Services REST API service is > standalone. There are several cross-cutting solutions that can be inherited > for free (kerberos, HA, ACLs, trusted proxy support, etc.) by the REST API > service if it is embedded into the RM process. In fact we can expose the REST > API via the same port as RM UI (8088 default). The URI path > /services/v1/applications will distinguish the REST API calls from other RM > APIs. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6623) Add support to turn off launching privileged containers in the container-executor
[
https://issues.apache.org/jira/browse/YARN-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178317#comment-16178317
]
Hadoop QA commented on YARN-6623:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
13s{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 13 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
50s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 13m
49s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 9m
30s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
59s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 3m
47s{color} | {color:green} trunk passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
44s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
14s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
11s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 5m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 5m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 5m
55s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
57s{color} | {color:green} hadoop-yarn-project/hadoop-yarn: The patch generated
0 new + 23 unchanged - 4 fixed = 23 total (was 27) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 3m
45s{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:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
12s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 74m 52s{color}
| {color:red} hadoop-yarn in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 14m
18s{color} | {color:green} hadoop-yarn-server-nodemanager in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
16s{color} | {color:green} hadoop-yarn-site in the patch passed. {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}147m 26s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:71bbb86 |
| JIRA Issue | YARN-6623 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12888749/YARN-6623.012.patch |
| Optional Tests | asflicense compile cc mvnsite javac unit javadoc
m
[jira] [Updated] (YARN-6943) Update Yarn to YARN in documentation
[ https://issues.apache.org/jira/browse/YARN-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetna Chaudhari updated YARN-6943: --- Attachment: YARN-6943-3.patch > Update Yarn to YARN in documentation > > > Key: YARN-6943 > URL: https://issues.apache.org/jira/browse/YARN-6943 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Miklos Szegedi >Assignee: Chetna Chaudhari >Priority: Minor > Labels: newbie > Attachments: YARN-6943-1.patch, YARN-6943-2.patch, YARN-6943-3.patch > > > Based on the discussion with [~templedf] in YARN-6757 the official case of > YARN is YARN, not Yarn, so we should update all the md files. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6943) Update Yarn to YARN in documentation
[ https://issues.apache.org/jira/browse/YARN-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetna Chaudhari updated YARN-6943: --- Attachment: (was: YARN-6943-2.patch) > Update Yarn to YARN in documentation > > > Key: YARN-6943 > URL: https://issues.apache.org/jira/browse/YARN-6943 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Miklos Szegedi >Assignee: Chetna Chaudhari >Priority: Minor > Labels: newbie > Attachments: YARN-6943-1.patch, YARN-6943-2.patch > > > Based on the discussion with [~templedf] in YARN-6757 the official case of > YARN is YARN, not Yarn, so we should update all the md files. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7240) Add more states and transitions to stabilize the NM Container state machine
[
https://issues.apache.org/jira/browse/YARN-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178282#comment-16178282
]
Hadoop QA commented on YARN-7240:
-
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
22s{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} 16m
57s{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
28s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
38s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
54s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
22s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
34s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
50s{color} | {color:green} the patch passed {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
0m 24s{color} | {color:orange}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:
The patch generated 33 new + 255 unchanged - 8 fixed = 288 total (was 263)
{color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
36s{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} findbugs {color} | {color:green} 1m
13s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
21s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 15m
7s{color} | {color:green} hadoop-yarn-server-nodemanager in the patch passed.
{color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
20s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 41m 38s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:71bbb86 |
| JIRA Issue | YARN-7240 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12888748/YARN-7240.001.patch |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux 721880b0ad64 3.13.0-129-generic #178-Ubuntu SMP Fri Aug 11
12:48:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / 415e5a1 |
| Default Java | 1.8.0_144 |
| findbugs | v3.1.0-RC1 |
| checkstyle |
https://builds.apache.org/job/PreCommit-YARN-Build/17614/artifact/patchprocess/diff-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-YARN-Build/17614/testReport/ |
| modules | C:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
U:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
|
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/17614/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> Add more states and transitions to stabilize the NM Container state machine
> ---
>
> Key: YARN-7240
> URL: htt
[jira] [Commented] (YARN-65) Reduce RM app memory footprint once app has completed
[
https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178280#comment-16178280
]
Hadoop QA commented on YARN-65:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{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 11 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 15m
0s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
35s{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
37s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
7s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
22s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
34s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
34s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
29s{color} | {color:green}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
The patch generated 0 new + 444 unchanged - 1 fixed = 444 total (was 445)
{color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
36s{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} findbugs {color} | {color:green} 1m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
19s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 44m 42s{color}
| {color:red} hadoop-yarn-server-resourcemanager in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 68m 33s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation |
| | hadoop.yarn.server.resourcemanager.scheduler.fair.TestFSAppStarvation |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:71bbb86 |
| JIRA Issue | YARN-65 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12888747/YARN-65.015.patch |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux 1665017242bf 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / 415e5a1 |
| Default Java | 1.8.0_144 |
| findbugs | v3.1.0-RC1 |
| unit |
https://builds.apache.org/job/PreCommit-YARN-Build/17613/artifact/patchprocess/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/17613/testReport/ |
| modules | C:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
U:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
|
| Console output |
https://builds.apache.org/job/PreCommit-YARN-Build/17613/console |
| Powered by | Apache Yetus 0.6.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> Reduce RM app memory f
[jira] [Comment Edited] (YARN-7240) Add more states and transitions to stabilize the NM Container state machine
[ https://issues.apache.org/jira/browse/YARN-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178270#comment-16178270 ] kartheek muthyala edited comment on YARN-7240 at 9/24/17 4:55 PM: -- Attaching the initial version of the patch with the following changes: 1. Adding a new UPDATE_CONTAINER_TOKEN state to the ContainerImpl class. 2. Splitting REINITALIZING to REINITIALIZING and REINITIALIZING_AWAITING_KILL [~asuresh], please review this initial patch and let me know incase if there are any further changes. was (Author: kartheek): Attaching the initial version of the patch with the following changes: 1. Adding a new UPDATE_CONTAINER_TOKEN state to the ContainerImpl class. 2. Renaming UpdateContainerSchedulerEvent to UpdateContainerTokenEvent 3. Splitting REINITALIZING to REINITIALIZING and REINITIALIZING_AWAITING_KILL [~asuresh], please review this initial patch and let me know incase if there are any further changes. > Add more states and transitions to stabilize the NM Container state machine > --- > > Key: YARN-7240 > URL: https://issues.apache.org/jira/browse/YARN-7240 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Arun Suresh >Assignee: kartheek muthyala > Attachments: YARN-7240.001.patch > > > There seem to be a few intermediate states that can be added to improve the > stability of the NM container state machine. > For. eg: > * The REINITIALIZING should probably be split into REINITIALIZING and > REINITIALIZING_AWAITING_KILL. > * Container updates are currently handled in the ContainerScheduler, but it > would probably be better to have it plumbed through the container state > machine as a new state, say UPDATING and a new container event. > The plan is to add some extra tests too to try and test every transition. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7243) Moving logging APIs over to slf4j in hadoop-yarn-server-resourcemanager
[
https://issues.apache.org/jira/browse/YARN-7243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178276#comment-16178276
]
Hadoop QA commented on YARN-7243:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{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 54 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 17m
28s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
34s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
12s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m
44s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
15s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
26s{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
39s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
39s{color} | {color:green}
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager
generated 0 new + 8 unchanged - 5 fixed = 8 total (was 13) {color} |
| {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange}
1m 10s{color} | {color:orange}
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
The patch generated 9 new + 3592 unchanged - 26 fixed = 3601 total (was 3618)
{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} findbugs {color} | {color:green} 1m
18s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
22s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 45m 17s{color}
| {color:red} hadoop-yarn-server-resourcemanager in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
14s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 74m 15s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Image:yetus/hadoop:71bbb86 |
| JIRA Issue | YARN-7243 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12888746/YARN-7243.003.patch |
| Optional Tests | asflicense compile javac javadoc mvninstall mvnsite
unit findbugs checkstyle |
| uname | Linux 4d95ff36d7c4 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /testptch/hadoop/patchprocess/precommit/personality/provided.sh
|
| git revision | trunk / 415e5a1 |
| Default Java | 1.8.0_144 |
| findbugs | v3.1.0-RC1 |
| checkstyle |
https://builds.apache.org/job/PreCommit-YARN-Build/17612/artifact/patchprocess/diff-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager.txt
|
| unit |
https://builds.apache.org/job/PreCommit-YARN-Build/17612/artifact/patchprocess/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/17612/testReport/ |
| modules | C:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
U:
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-
[jira] [Updated] (YARN-6623) Add support to turn off launching privileged containers in the container-executor
[ https://issues.apache.org/jira/browse/YARN-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-6623: Attachment: YARN-6623.012.patch Uploaded 012.patch to fix cc and unit test issues. > Add support to turn off launching privileged containers in the > container-executor > - > > Key: YARN-6623 > URL: https://issues.apache.org/jira/browse/YARN-6623 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager >Reporter: Varun Vasudev >Assignee: Varun Vasudev >Priority: Blocker > Attachments: YARN-6623.001.patch, YARN-6623.002.patch, > YARN-6623.003.patch, YARN-6623.004.patch, YARN-6623.005.patch, > YARN-6623.006.patch, YARN-6623.007.patch, YARN-6623.008.patch, > YARN-6623.009.patch, YARN-6623.010.patch, YARN-6623.011.patch, > YARN-6623.012.patch > > > Currently, launching privileged containers is controlled by the NM. We should > add a flag to the container-executor.cfg allowing admins to disable launching > privileged containers at the container-executor level. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7240) Add more states and transitions to stabilize the NM Container state machine
[ https://issues.apache.org/jira/browse/YARN-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kartheek muthyala updated YARN-7240: Attachment: YARN-7240.001.patch Attaching the initial version of the patch with the following changes: 1. Adding a new UPDATE_CONTAINER_TOKEN state to the ContainerImpl class. 2. Renaming UpdateContainerSchedulerEvent to UpdateContainerTokenEvent 3. Splitting REINITALIZING to REINITIALIZING and REINITIALIZING_AWAITING_KILL [~asuresh], please review this initial patch and let me know incase if there are any further changes. > Add more states and transitions to stabilize the NM Container state machine > --- > > Key: YARN-7240 > URL: https://issues.apache.org/jira/browse/YARN-7240 > Project: Hadoop YARN > Issue Type: Improvement >Reporter: Arun Suresh >Assignee: kartheek muthyala > Attachments: YARN-7240.001.patch > > > There seem to be a few intermediate states that can be added to improve the > stability of the NM container state machine. > For. eg: > * The REINITIALIZING should probably be split into REINITIALIZING and > REINITIALIZING_AWAITING_KILL. > * Container updates are currently handled in the ContainerScheduler, but it > would probably be better to have it plumbed through the container state > machine as a new state, say UPDATING and a new container event. > The plan is to add some extra tests too to try and test every transition. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6623) Add support to turn off launching privileged containers in the container-executor
[
https://issues.apache.org/jira/browse/YARN-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178263#comment-16178263
]
Hadoop QA commented on YARN-6623:
-
| (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 13 new or modified test
files. {color} |
|| || || || {color:brown} trunk Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
43s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 13m
44s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 10m
2s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
2s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 4m
3s{color} | {color:green} trunk passed {color} |
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
47s{color} | {color:green} trunk passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
17s{color} | {color:green} trunk passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
10s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 6m
30s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} cc {color} | {color:red} 6m 30s{color} |
{color:red} hadoop-yarn-project_hadoop-yarn generated 2 new + 0 unchanged - 0
fixed = 2 total (was 0) {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 6m
30s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
56s{color} | {color:green} hadoop-yarn-project/hadoop-yarn: The patch generated
0 new + 23 unchanged - 4 fixed = 23 total (was 27) {color} |
| {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 3m
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:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Skipped patched modules with no Java source:
hadoop-yarn-project/hadoop-yarn
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m
51s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
8s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 74m 48s{color}
| {color:red} hadoop-yarn in the patch failed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 14m 29s{color}
| {color:red} hadoop-yarn-server-nodemanager in the patch failed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
24s{color} | {color:green} hadoop-yarn-site in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
44s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}149m 54s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation |
| |
hadoop.yarn.server.nodemanager.containermanager.linux.runtime.TestDockerContainerRuntime
|
| |
hadoop.yarn.server.nodemanager.containermanager.linux.runtime.TestDockerContainerRuntime
|
\\
\\
|| Subsystem || Report/
[jira] [Commented] (YARN-65) Reduce RM app memory footprint once app has completed
[
https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178261#comment-16178261
]
Manikandan R commented on YARN-65:
--
Fixed checkstyle and whitespace issues. Junit failures is not related to this
patch as explained earlier.
> Reduce RM app memory footprint once app has completed
> -
>
> Key: YARN-65
> URL: https://issues.apache.org/jira/browse/YARN-65
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 0.23.3
>Reporter: Jason Lowe
>Assignee: Manikandan R
> Attachments: YARN-65.001.patch, YARN-65.002.patch, YARN-65.003.patch,
> YARN-65.004.patch, YARN-65.005.patch, YARN-65.006.patch, YARN-65.007.patch,
> YARN-65.008.patch, YARN-65.009.patch, YARN-65.010.patch, YARN-65.011.patch,
> YARN-65.012.patch, YARN-65.013.patch, YARN-65.014.patch, YARN-65.015.patch
>
>
> The ResourceManager holds onto a configurable number of completed
> applications (yarn.resource.max-completed-applications, defaults to 1),
> and the memory footprint of these completed applications can be significant.
> For example, the {{submissionContext}} in RMAppImpl contains references to
> protocolbuffer objects and other items that probably aren't necessary to keep
> around once the application has completed. We could significantly reduce the
> memory footprint of the RM by releasing objects that are no longer necessary
> once an application completes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-65) Reduce RM app memory footprint once app has completed
[
https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikandan R updated YARN-65:
-
Attachment: YARN-65.015.patch
> Reduce RM app memory footprint once app has completed
> -
>
> Key: YARN-65
> URL: https://issues.apache.org/jira/browse/YARN-65
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
>Affects Versions: 0.23.3
>Reporter: Jason Lowe
>Assignee: Manikandan R
> Attachments: YARN-65.001.patch, YARN-65.002.patch, YARN-65.003.patch,
> YARN-65.004.patch, YARN-65.005.patch, YARN-65.006.patch, YARN-65.007.patch,
> YARN-65.008.patch, YARN-65.009.patch, YARN-65.010.patch, YARN-65.011.patch,
> YARN-65.012.patch, YARN-65.013.patch, YARN-65.014.patch, YARN-65.015.patch
>
>
> The ResourceManager holds onto a configurable number of completed
> applications (yarn.resource.max-completed-applications, defaults to 1),
> and the memory footprint of these completed applications can be significant.
> For example, the {{submissionContext}} in RMAppImpl contains references to
> protocolbuffer objects and other items that probably aren't necessary to keep
> around once the application has completed. We could significantly reduce the
> memory footprint of the RM by releasing objects that are no longer necessary
> once an application completes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-7243) Moving logging APIs over to slf4j in hadoop-yarn-server-resourcemanager
[
https://issues.apache.org/jira/browse/YARN-7243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178252#comment-16178252
]
Yeliang Cang commented on YARN-7243:
Submit patch003! Fix some checkstyles.
I leave the
{code}
Name 'LOG' must match pattern '^[a-z][a-zA-Z0-9]*$'.
{code}
unchanged...
> Moving logging APIs over to slf4j in hadoop-yarn-server-resourcemanager
> ---
>
> Key: YARN-7243
> URL: https://issues.apache.org/jira/browse/YARN-7243
> Project: Hadoop YARN
> Issue Type: Sub-task
>Reporter: Yeliang Cang
>Assignee: Yeliang Cang
> Attachments: YARN-7243.001.patch, YARN-7243.002.patch,
> YARN-7243.003.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
-
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-7243) Moving logging APIs over to slf4j in hadoop-yarn-server-resourcemanager
[ https://issues.apache.org/jira/browse/YARN-7243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yeliang Cang updated YARN-7243: --- Attachment: YARN-7243.003.patch > Moving logging APIs over to slf4j in hadoop-yarn-server-resourcemanager > --- > > Key: YARN-7243 > URL: https://issues.apache.org/jira/browse/YARN-7243 > Project: Hadoop YARN > Issue Type: Sub-task >Reporter: Yeliang Cang >Assignee: Yeliang Cang > Attachments: YARN-7243.001.patch, YARN-7243.002.patch, > YARN-7243.003.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Updated] (YARN-6623) Add support to turn off launching privileged containers in the container-executor
[ https://issues.apache.org/jira/browse/YARN-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-6623: Attachment: YARN-6623.011.patch Uploaded a new patch (.011). It adds support for group-add and adds documentation for the container-executor.cfg settings. [~ebadger] - can you please take a look at the group-add changes and confirm they're ok? > Add support to turn off launching privileged containers in the > container-executor > - > > Key: YARN-6623 > URL: https://issues.apache.org/jira/browse/YARN-6623 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager >Reporter: Varun Vasudev >Assignee: Varun Vasudev >Priority: Blocker > Attachments: YARN-6623.001.patch, YARN-6623.002.patch, > YARN-6623.003.patch, YARN-6623.004.patch, YARN-6623.005.patch, > YARN-6623.006.patch, YARN-6623.007.patch, YARN-6623.008.patch, > YARN-6623.009.patch, YARN-6623.010.patch, YARN-6623.011.patch > > > Currently, launching privileged containers is controlled by the NM. We should > add a flag to the container-executor.cfg allowing admins to disable launching > privileged containers at the container-executor level. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-6504) Add support for resource profiles in MapReduce
[ https://issues.apache.org/jira/browse/YARN-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178183#comment-16178183 ] Varun Vasudev commented on YARN-6504: - I had a bunch of conversations about whether we should support override capabilities. My reason for adding it in the end is that without overrides, every existing job has to be re-written and re-tested, etc to match the profiles the admin creates. However, I'm in heavy favor of allowing overrides for memory and vcores only and not letting users override other resource types. > Add support for resource profiles in MapReduce > -- > > Key: YARN-6504 > URL: https://issues.apache.org/jira/browse/YARN-6504 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, resourcemanager >Reporter: Varun Vasudev >Assignee: Varun Vasudev > Attachments: YARN-6504-YARN-3926.001.patch, > YARN-6504.YARN-3926.002.patch, YARN-6504.YARN-3926.003.patch > > -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
