[jira] [Updated] (YARN-10381) Send out application attempt state along with other elements in the application attempt object returned from appattempts REST API call

[ https://issues.apache.org/jira/browse/YARN-10381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Ahuja updated YARN-10381: --- Component/s: yarn-ui-v2 > Send out application attempt state along with other elements in the

[jira] [Updated] (YARN-10381) Send out application attempt state along with other elements in the application attempt object returned from appattempts REST API call

[ https://issues.apache.org/jira/browse/YARN-10381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Ahuja updated YARN-10381: --- Affects Version/s: 3.3.0 > Send out application attempt state along with other elements in th

[jira] [Created] (YARN-10381) Send out application attempt state along with other elements in the application attempt object returned from appattempts REST API call

Siddharth Ahuja created YARN-10381: -- Summary: Send out application attempt state along with other elements in the application attempt object returned from appattempts REST API call Key: YARN-10381 URL: https://i

[jira] [Assigned] (YARN-10381) Send out application attempt state along with other elements in the application attempt object returned from appattempts REST API call

[ https://issues.apache.org/jira/browse/YARN-10381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Ahuja reassigned YARN-10381: -- Assignee: Siddharth Ahuja > Send out application attempt state along with other elemen

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

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

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168317#comment-17168317 ] Íñigo Goiri commented on YARN-10229: +1 on [^YARN-10229.008.patch]. > [Federation]

[jira] [Commented] (YARN-1529) Add Localization overhead metrics to NM

[ https://issues.apache.org/jira/browse/YARN-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168213#comment-17168213 ] Jim Brennan commented on YARN-1529: --- Thanks [~epayne]! > Add Localization overhead metr

[jira] [Commented] (YARN-1529) Add Localization overhead metrics to NM

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

[jira] [Comment Edited] (YARN-4575) ApplicationResourceUsageReport should return ALL reserved resource

[ https://issues.apache.org/jira/browse/YARN-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168205#comment-17168205 ] Eric Payne edited comment on YARN-4575 at 7/30/20, 8:45 PM: I'

[jira] [Commented] (YARN-4575) ApplicationResourceUsageReport should return ALL reserved resource

[ https://issues.apache.org/jira/browse/YARN-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168205#comment-17168205 ] Eric Payne commented on YARN-4575: -- I'm not sure why 2 pre-commit builds are being trigge

[jira] [Commented] (YARN-1529) Add Localization overhead metrics to NM

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

[jira] [Updated] (YARN-1529) Add Localization overhead metrics to NM

[ https://issues.apache.org/jira/browse/YARN-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-1529: - Fix Version/s: 3.1.5 3.3.1 3.4.0 2.10.1

[jira] [Commented] (YARN-1529) Add Localization overhead metrics to NM

[ https://issues.apache.org/jira/browse/YARN-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168161#comment-17168161 ] Jim Brennan commented on YARN-1529: --- [~epayne] I have uploaded a patch for branch-2.10. 

[jira] [Updated] (YARN-1529) Add Localization overhead metrics to NM

[ https://issues.apache.org/jira/browse/YARN-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-1529: -- Attachment: YARN-1529-branch-2.10.001.patch > Add Localization overhead metrics to NM >

[jira] [Commented] (YARN-1529) Add Localization overhead metrics to NM

[ https://issues.apache.org/jira/browse/YARN-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168136#comment-17168136 ] Jim Brennan commented on YARN-1529: --- Thanks [~epayne]!  I will put up a patch for branch

[jira] [Commented] (YARN-1529) Add Localization overhead metrics to NM

[ https://issues.apache.org/jira/browse/YARN-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168122#comment-17168122 ] Eric Payne commented on YARN-1529: -- I don't know why 2 pre-commit builds were kicked off.

[jira] [Commented] (YARN-10380) Import logic of multi-node allocation in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-10380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168116#comment-17168116 ] Wangda Tan commented on YARN-10380: --- cc: [~prabhujoseph], I think we identified more is

[jira] [Created] (YARN-10380) Import logic of multi-node allocation in CapacityScheduler

Wangda Tan created YARN-10380: - Summary: Import logic of multi-node allocation in CapacityScheduler Key: YARN-10380 URL: https://issues.apache.org/jira/browse/YARN-10380 Project: Hadoop YARN Issu

[jira] [Created] (YARN-10379) Refactor ContainerExecutor exit code Exception handling

Benjamin Teke created YARN-10379: Summary: Refactor ContainerExecutor exit code Exception handling Key: YARN-10379 URL: https://issues.apache.org/jira/browse/YARN-10379 Project: Hadoop YARN I

[jira] [Commented] (YARN-1529) Add Localization overhead metrics to NM

[ https://issues.apache.org/jira/browse/YARN-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17168064#comment-17168064 ] Hudson commented on YARN-1529: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #184

[jira] [Updated] (YARN-4783) Log aggregation failure for application when Nodemanager is restarted

[ https://issues.apache.org/jira/browse/YARN-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori updated YARN-4783: --- Attachment: YARN-4783.001.patch > Log aggregation failure for application when Nodemanager is restarte

[jira] [Reopened] (YARN-4783) Log aggregation failure for application when Nodemanager is restarted

[ https://issues.apache.org/jira/browse/YARN-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori reopened YARN-4783: I am reopening this issue in order to find a less invasive approach on how to handle this corner case,

[jira] [Assigned] (YARN-4783) Log aggregation failure for application when Nodemanager is restarted

[ https://issues.apache.org/jira/browse/YARN-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Gyori reassigned YARN-4783: -- Assignee: Andras Gyori > Log aggregation failure for application when Nodemanager is restarted

[jira] [Commented] (YARN-9136) getNMResourceInfo NodeManager REST API method is not documented

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

[jira] [Commented] (YARN-9136) getNMResourceInfo NodeManager REST API method is not documented

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

[jira] [Resolved] (YARN-10378) When NM goes down and comes back up, PC allocation tags are not removed for completed containers

[ https://issues.apache.org/jira/browse/YARN-10378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tarun Parimi resolved YARN-10378. - Resolution: Duplicate Looks like YARN-10034 fixes this issue for NM going down scenario also. Clo

[jira] [Updated] (YARN-9136) getNMResourceInfo NodeManager REST API method is not documented

[ https://issues.apache.org/jira/browse/YARN-9136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hudáky Márton Gyula updated YARN-9136: -- Attachment: YARN-9136.002.patch > getNMResourceInfo NodeManager REST API method is not d