[jira] [Commented] (YARN-10540) Node page is broken in YARN UI1 and UI2 including RMWebService api for nodes

[ https://issues.apache.org/jira/browse/YARN-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253117#comment-17253117 ] Jim Brennan commented on YARN-10540: I filed YARN-10542 as a follow-up. > Node page is broken in

[jira] [Commented] (YARN-10540) Node page is broken in YARN UI1 and UI2 including RMWebService api for nodes

[ https://issues.apache.org/jira/browse/YARN-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253090#comment-17253090 ] Jim Brennan commented on YARN-10540: I have manually reproduced this in trunk on a VM by setting the

[jira] [Assigned] (YARN-10540) Node page is broken in YARN UI1 and UI2 including RMWebService api for nodes

[ https://issues.apache.org/jira/browse/YARN-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan reassigned YARN-10540: -- Assignee: Jim Brennan I have attached a patch that initializes nodeUtilization to a

[jira] [Commented] (YARN-10540) Node page is broken in YARN UI1 and UI2 including RMWebService api for nodes

[ https://issues.apache.org/jira/browse/YARN-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253150#comment-17253150 ] Hadoop QA commented on YARN-10540: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Created] (YARN-10542) Node Utilization on UI is misleading if nodes don't report utilization

Jim Brennan created YARN-10542: -- Summary: Node Utilization on UI is misleading if nodes don't report utilization Key: YARN-10542 URL: https://issues.apache.org/jira/browse/YARN-10542 Project: Hadoop

[jira] [Commented] (YARN-10528) maxAMShare should only be accepted for leaf queues, not parent queues

[ https://issues.apache.org/jira/browse/YARN-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253159#comment-17253159 ] Siddharth Ahuja commented on YARN-10528: Hi [~snemeth], trunk and 3.3 are all good, whereas, test

[jira] [Updated] (YARN-10540) Node page is broken in YARN UI1 and UI2 including RMWebService api for nodes

[ https://issues.apache.org/jira/browse/YARN-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-10540: --- Fix Version/s: 3.2.3 2.10.2 3.1.5 3.3.1

[jira] [Updated] (YARN-10540) Node page is broken in YARN UI1 and UI2 including RMWebService api for nodes

[ https://issues.apache.org/jira/browse/YARN-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-10540: --- Attachment: YARN-10540.001.patch > Node page is broken in YARN UI1 and UI2 including RMWebService

[jira] [Updated] (YARN-10541) capture the performance metrics of ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-10541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YARN-10541: -- Labels: pull-request-available (was: ) > capture the performance metrics of ZKRMStateStore >

[jira] [Created] (YARN-10541) capture the performance metrics of ZKRMStateStore

Max Xie created YARN-10541: --- Summary: capture the performance metrics of ZKRMStateStore Key: YARN-10541 URL: https://issues.apache.org/jira/browse/YARN-10541 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-10528) maxAMShare should only be accepted for leaf queues, not parent queues

[ https://issues.apache.org/jira/browse/YARN-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252695#comment-17252695 ] Hadoop QA commented on YARN-10528: -- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-10528) maxAMShare should only be accepted for leaf queues, not parent queues

[ https://issues.apache.org/jira/browse/YARN-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252715#comment-17252715 ] Hadoop QA commented on YARN-10528: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-10528) maxAMShare should only be accepted for leaf queues, not parent queues

[ https://issues.apache.org/jira/browse/YARN-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Ahuja updated YARN-10528: --- Attachment: YARN-10528-branch-3.3.001.patch > maxAMShare should only be accepted for leaf

[jira] [Updated] (YARN-10528) maxAMShare should only be accepted for leaf queues, not parent queues

[ https://issues.apache.org/jira/browse/YARN-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Ahuja updated YARN-10528: --- Attachment: (was: YARN-10528-branch-3.3.001.patch) > maxAMShare should only be accepted

[jira] [Commented] (YARN-10528) maxAMShare should only be accepted for leaf queues, not parent queues

[ https://issues.apache.org/jira/browse/YARN-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252730#comment-17252730 ] Hadoop QA commented on YARN-10528: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-10528) maxAMShare should only be accepted for leaf queues, not parent queues

[ https://issues.apache.org/jira/browse/YARN-10528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252830#comment-17252830 ] Hadoop QA commented on YARN-10528: -- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-10506) Update queue creation logic to use weight mode and allow the flexible static/dynamic creation

[ https://issues.apache.org/jira/browse/YARN-10506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252919#comment-17252919 ] zhuqi commented on YARN-10506: -- [~wangda] [~gandras] When i deep into some test in 

[jira] [Commented] (YARN-10540) Node page is broken in YARN UI1 and UI2 including RMWebService api for nodes

[ https://issues.apache.org/jira/browse/YARN-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253003#comment-17253003 ] Jim Brennan commented on YARN-10540: Trying to figure out why we might get an NPE in this case. One

[jira] [Commented] (YARN-10540) Node page is broken in YARN UI1 and UI2 including RMWebService api for nodes

[ https://issues.apache.org/jira/browse/YARN-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253018#comment-17253018 ] Jim Brennan commented on YARN-10540: Just to clarify, we are seeing this only on Mac in branch-3.2.2?

[jira] [Commented] (YARN-10540) Node page is broken in YARN UI1 and UI2 including RMWebService api for nodes

[ https://issues.apache.org/jira/browse/YARN-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17253022#comment-17253022 ] Jim Brennan commented on YARN-10540: Simpler fix might be to initialize {{nodeUtilization}} in

[jira] [Assigned] (YARN-10544) AMParams.java having un-necessary access identifier static final

[ https://issues.apache.org/jira/browse/YARN-10544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ANANDA G B reassigned YARN-10544: - Assignee: ANANDA G B > AMParams.java having un-necessary access identifier static final >

[jira] [Created] (YARN-10544) AMParams.java having un-necessary access identifier static final

ANANDA G B created YARN-10544: - Summary: AMParams.java having un-necessary access identifier static final Key: YARN-10544 URL: https://issues.apache.org/jira/browse/YARN-10544 Project: Hadoop YARN

[jira] [Assigned] (YARN-10543) Timeline Server V1.5 not supporting audit log

[ https://issues.apache.org/jira/browse/YARN-10543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ANANDA G B reassigned YARN-10543: - Assignee: ANANDA G B > Timeline Server V1.5 not supporting audit log >

[jira] [Created] (YARN-10543) Timeline Server V1.5 not supporting audit log

ANANDA G B created YARN-10543: - Summary: Timeline Server V1.5 not supporting audit log Key: YARN-10543 URL: https://issues.apache.org/jira/browse/YARN-10543 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-10538) Add recommissioning nodes to the list of updated nodes returned to the AM

[ https://issues.apache.org/jira/browse/YARN-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252751#comment-17252751 ] Hadoop QA commented on YARN-10538: -- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-10540) Node page is broken in YARN UI1 and UI2 including RMWebService api for nodes

[ https://issues.apache.org/jira/browse/YARN-10540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252953#comment-17252953 ] Sunil G commented on YARN-10540: [~Jim_Brennan] [~ebadger] pls share your thoughts as we see this NPE

[jira] [Comment Edited] (YARN-10506) Update queue creation logic to use weight mode and allow the flexible static/dynamic creation

[ https://issues.apache.org/jira/browse/YARN-10506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252919#comment-17252919 ] zhuqi edited comment on YARN-10506 at 12/21/20, 3:30 PM: - [~wangda] [~gandras]

[jira] [Commented] (YARN-10506) Update queue creation logic to use weight mode and allow the flexible static/dynamic creation

[ https://issues.apache.org/jira/browse/YARN-10506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17252934#comment-17252934 ] Andras Gyori commented on YARN-10506: - Thank you [~zhuqi] for the feedback! I intend to upload a new