[jira] [Created] (YARN-10344) Sync netty-* versions in hadoop-yarn-csi

Akira Ajisaka created YARN-10344: Summary: Sync netty-* versions in hadoop-yarn-csi Key: YARN-10344 URL: https://issues.apache.org/jira/browse/YARN-10344 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-10344) Sync netty versions in hadoop-yarn-csi

[ https://issues.apache.org/jira/browse/YARN-10344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YARN-10344: - Summary: Sync netty versions in hadoop-yarn-csi (was: Sync netty-* versions in hadoop-yarn-csi)

[jira] [Commented] (YARN-10340) HsWebServices getContainerReport uses loginUser instead of remoteUser to access ApplicationClientProtocol

[ https://issues.apache.org/jira/browse/YARN-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153225#comment-17153225 ] Tarun Parimi commented on YARN-10340: - [~prabhujoseph], The issue is because the

[jira] [Assigned] (YARN-10344) Sync netty versions in hadoop-yarn-csi

[ https://issues.apache.org/jira/browse/YARN-10344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YARN-10344: Assignee: Akira Ajisaka > Sync netty versions in hadoop-yarn-csi >

[jira] [Updated] (YARN-10343) Legacy RM UI should include labeled metrics for allocated, total, and reserved resources.

[ https://issues.apache.org/jira/browse/YARN-10343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10343: -- Attachment: Screen Shot 2020-07-07 at 1.03.26 PM.png > Legacy RM UI should include labeled metrics for

[jira] [Updated] (YARN-10343) Legacy RM UI should include labeled metrics for allocated, total, and reserved resources.

[ https://issues.apache.org/jira/browse/YARN-10343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10343: -- Description: The current legacy RM UI only includes resources metrics for the default partition. If a

[jira] [Updated] (YARN-10344) Sync netty versions in hadoop-yarn-csi

[ https://issues.apache.org/jira/browse/YARN-10344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YARN-10344: - Affects Version/s: 3.3.0 > Sync netty versions in hadoop-yarn-csi >

[jira] [Created] (YARN-10343) Legacy RM UI should include labeled metrics for allocated, total, and reserved resources.

Eric Payne created YARN-10343: - Summary: Legacy RM UI should include labeled metrics for allocated, total, and reserved resources. Key: YARN-10343 URL: https://issues.apache.org/jira/browse/YARN-10343

[jira] [Commented] (YARN-10344) Sync netty-* versions in hadoop-yarn-csi

[ https://issues.apache.org/jira/browse/YARN-10344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153178#comment-17153178 ] Akira Ajisaka commented on YARN-10344: -- Given hadoop-yarn-csi module directly depends on netty-all,

[jira] [Commented] (YARN-10343) Legacy RM UI should include labeled metrics for allocated, total, and reserved resources.

[ https://issues.apache.org/jira/browse/YARN-10343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153098#comment-17153098 ] Eric Payne commented on YARN-10343: --- I see two major problems with this structure: - Resource metrics

[jira] [Updated] (YARN-10343) Legacy RM UI should include labeled metrics for allocated, total, and reserved resources.

[ https://issues.apache.org/jira/browse/YARN-10343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-10343: -- Attachment: Screen Shot 2020-07-07 at 1.00.22 PM.png > Legacy RM UI should include labeled metrics for

[jira] [Commented] (YARN-10335) Improve scheduling of containers based on node health

[ https://issues.apache.org/jira/browse/YARN-10335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153234#comment-17153234 ] Bibin Chundatt commented on YARN-10335: --- Thank you [~cyrusjackson25] for working in this Few

[jira] [Commented] (YARN-10340) HsWebServices getContainerReport uses loginUser instead of remoteUser to access ApplicationClientProtocol

[ https://issues.apache.org/jira/browse/YARN-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153240#comment-17153240 ] Prabhu Joseph commented on YARN-10340: -- Thanks [~tarunparimi] for the analysis. bq. This creates a

[jira] [Commented] (YARN-10339) Timeline Client in Nodemanager gets 403 errors when simple auth is used in kerberos environments

[ https://issues.apache.org/jira/browse/YARN-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152527#comment-17152527 ] Prabhu Joseph commented on YARN-10339: -- [~tarunparimi] Thanks for the patch. The patch looks good.

[jira] [Commented] (YARN-10340) HsWebServices getContainerReport uses loginUser instead of remoteUser to access ApplicationClientProtocol

[ https://issues.apache.org/jira/browse/YARN-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152501#comment-17152501 ] Tarun Parimi commented on YARN-10340: - [~prabhujoseph],[~brahmareddy] The WebServices#getContainer

[jira] [Updated] (YARN-10339) Timeline Client in Nodemanager gets 403 errors when simple auth is used in kerberos environments

[ https://issues.apache.org/jira/browse/YARN-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tarun Parimi updated YARN-10339: Attachment: YARN-10339.002.patch > Timeline Client in Nodemanager gets 403 errors when simple auth

[jira] [Commented] (YARN-10339) Timeline Client in Nodemanager gets 403 errors when simple auth is used in kerberos environments

[ https://issues.apache.org/jira/browse/YARN-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152548#comment-17152548 ] Tarun Parimi commented on YARN-10339: - Thanks [~prabhujoseph] . When atsv1 is enabled, delegation

[jira] [Comment Edited] (YARN-10339) Timeline Client in Nodemanager gets 403 errors when simple auth is used in kerberos environments

[ https://issues.apache.org/jira/browse/YARN-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152548#comment-17152548 ] Tarun Parimi edited comment on YARN-10339 at 7/7/20, 8:17 AM: -- Thanks

[jira] [Commented] (YARN-10339) Timeline Client in Nodemanager gets 403 errors when simple auth is used in kerberos environments

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

[jira] [Commented] (YARN-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152719#comment-17152719 ] Bilwa S T commented on YARN-10337: -- Thanks [~prabhujoseph] > TestRMHATimelineCollectors fails on hadoop

[jira] [Created] (YARN-10342) [UI1] Provide a way to hide Tools section in Web UIv1

Andras Gyori created YARN-10342: --- Summary: [UI1] Provide a way to hide Tools section in Web UIv1 Key: YARN-10342 URL: https://issues.apache.org/jira/browse/YARN-10342 Project: Hadoop YARN

[jira] [Updated] (YARN-8047) RMWebApp make external class pluggable

[ https://issues.apache.org/jira/browse/YARN-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-8047: Attachment: YARN-8047.006.patch > RMWebApp make external class pluggable >

[jira] [Commented] (YARN-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152680#comment-17152680 ] Prabhu Joseph commented on YARN-10337: -- Thanks [~BilwaST] for the patch. +1, have committed it to

[jira] [Updated] (YARN-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-10337: - Parent: YARN-9802 Issue Type: Sub-task (was: Bug) > TestRMHATimelineCollectors fails on

[jira] [Commented] (YARN-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152693#comment-17152693 ] Hudson commented on YARN-10337: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #18416 (See

[jira] [Commented] (YARN-8047) RMWebApp make external class pluggable

[ https://issues.apache.org/jira/browse/YARN-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152718#comment-17152718 ] Bilwa S T commented on YARN-8047: - Thanks [~prabhujoseph] for reviewing. I have handled all comments . Is

[jira] [Commented] (YARN-10106) Yarn logs CLI filtering by application attempt

[ https://issues.apache.org/jira/browse/YARN-10106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152777#comment-17152777 ] Benjamin Teke commented on YARN-10106: -- Hi [~mhudaky], Thanks for the patch! It generally looks

[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed

[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152749#comment-17152749 ] Brahma Reddy Battula commented on YARN-10341: - [~BilwaST] thanks for reporting. Looks to be

[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed

[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152870#comment-17152870 ] Billie Rinaldi commented on YARN-10341: --- I agree, continue looks better here. > Yarn Service

[jira] [Commented] (YARN-8047) RMWebApp make external class pluggable

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