[jira] [Commented] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500513#comment-14500513 ] Hadoop QA commented on YARN-2003: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3410) YARN admin should be able to remove individual application records from RMStateStore

[ https://issues.apache.org/jira/browse/YARN-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500526#comment-14500526 ] Rohith commented on YARN-3410: -- All tests failed with BindException.. Jenkins need to kick off

[jira] [Commented] (YARN-3491) PublicLocalizer#addResource is too slow.

[ https://issues.apache.org/jira/browse/YARN-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500433#comment-14500433 ] Hadoop QA commented on YARN-3491: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3410) YARN admin should be able to remove individual application records from RMStateStore

[ https://issues.apache.org/jira/browse/YARN-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500501#comment-14500501 ] Hadoop QA commented on YARN-3410: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500506#comment-14500506 ] Sunil G commented on YARN-3136: --- Hi [~jianhe] I used below suppression {noformat} Match

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily

[ https://issues.apache.org/jira/browse/YARN-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500484#comment-14500484 ] Hadoop QA commented on YARN-3487: - {color:red}-1 overall{color}. Here are the results of

[jira] [Created] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

Junping Du created YARN-3505: Summary: Node's Log Aggregation Report with SUCCEED should not cached in RMApps Key: YARN-3505 URL: https://issues.apache.org/jira/browse/YARN-3505 Project: Hadoop YARN

[jira] [Commented] (YARN-1402) Related Web UI, CLI changes on exposing client API to check log aggregation status

[ https://issues.apache.org/jira/browse/YARN-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500580#comment-14500580 ] Hudson commented on YARN-1402: -- FAILURE: Integrated in Hadoop-trunk-Commit #7606 (See

[jira] [Updated] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

[ https://issues.apache.org/jira/browse/YARN-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3493: -- Attachment: YARN-3493.4.patch RM fails to come up with error Failed to load/recover state when mem settings

[jira] [Updated] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2003: -- Attachment: 0008-YARN-2003.patch Fixing a test issue. Support to process Job priority from Submission Context

[jira] [Updated] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3136: -- Attachment: 00013-YARN-3136.patch getTransferredContainers can be a bottleneck during AM registration

[jira] [Commented] (YARN-2696) Queue sorting in CapacityScheduler should consider node label

[ https://issues.apache.org/jira/browse/YARN-2696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500631#comment-14500631 ] Hudson commented on YARN-2696: -- FAILURE: Integrated in Hadoop-trunk-Commit #7607 (See

[jira] [Commented] (YARN-3431) Sub resources of timeline entity needs to be passed to a separate endpoint.

[ https://issues.apache.org/jira/browse/YARN-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500672#comment-14500672 ] Zhijie Shen commented on YARN-3431: --- [~sjlee0], how about we doing this? Instead of using

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500680#comment-14500680 ] Jian He commented on YARN-3136: --- Hi [~sunilg], we can suppress at the filed level. Just

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily

[ https://issues.apache.org/jira/browse/YARN-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500767#comment-14500767 ] Wangda Tan commented on YARN-3487: -- Re-triggerred Jenkins CapacityScheduler scheduler

[jira] [Commented] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

[ https://issues.apache.org/jira/browse/YARN-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500787#comment-14500787 ] Wangda Tan commented on YARN-3493: -- Some comments: - validateResourceRequest -

[jira] [Updated] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

[ https://issues.apache.org/jira/browse/YARN-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3493: -- Attachment: (was: YARN-3493.5.patch) RM fails to come up with error Failed to load/recover state when mem

[jira] [Updated] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

[ https://issues.apache.org/jira/browse/YARN-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3493: -- Attachment: YARN-3493.5.patch Thanks for the review. updated the patch accordingly RM fails to come up with

[jira] [Commented] (YARN-3451) Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

[ https://issues.apache.org/jira/browse/YARN-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500867#comment-14500867 ] Hudson commented on YARN-3451: -- FAILURE: Integrated in Hadoop-trunk-Commit #7608 (See

[jira] [Commented] (YARN-3497) ContainerManagementProtocolProxy modifies IPC timeout conf without making a copy

[ https://issues.apache.org/jira/browse/YARN-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500873#comment-14500873 ] Jian He commented on YARN-3497: --- should we change below to use this.conf as well ? {code}

[jira] [Updated] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

[ https://issues.apache.org/jira/browse/YARN-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3493: -- Attachment: YARN-3493.5.patch RM fails to come up with error Failed to load/recover state when mem settings

[jira] [Commented] (YARN-3451) Add start time and Elapsed in ApplicationAttemptReport and display the same in RMAttemptBlock WebUI

[ https://issues.apache.org/jira/browse/YARN-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500843#comment-14500843 ] Jian He commented on YARN-3451: --- looks good, +1 Add start time and Elapsed in

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily

[ https://issues.apache.org/jira/browse/YARN-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500891#comment-14500891 ] Hadoop QA commented on YARN-3487: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3482) Report NM available resources in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500894#comment-14500894 ] Inigo Goiri commented on YARN-3482: --- Hi Sunil G, yes, I'm talking about Total CPU and

[jira] [Commented] (YARN-3410) YARN admin should be able to remove individual application records from RMStateStore

[ https://issues.apache.org/jira/browse/YARN-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500795#comment-14500795 ] Hadoop QA commented on YARN-3410: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3437) convert load test driver to timeline service v.2

[ https://issues.apache.org/jira/browse/YARN-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500088#comment-14500088 ] Sangjin Lee commented on YARN-3437: --- Thanks [~zjshen]! Could someone please commit this

[jira] [Commented] (YARN-1402) Related Web UI, CLI changes on exposing client API to check log aggregation status

[ https://issues.apache.org/jira/browse/YARN-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500164#comment-14500164 ] Xuan Gong commented on YARN-1402: - Yes, file YARN-3504 to track this testcase failure

[jira] [Commented] (YARN-3410) YARN admin should be able to remove individual application records from RMStateStore

[ https://issues.apache.org/jira/browse/YARN-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500125#comment-14500125 ] Rohith commented on YARN-3410: -- Thanks [~leftnoteasy] for review.. Updated the patch that

[jira] [Created] (YARN-3504) TestRMRestart fails occasionally in trunk

Xuan Gong created YARN-3504: --- Summary: TestRMRestart fails occasionally in trunk Key: YARN-3504 URL: https://issues.apache.org/jira/browse/YARN-3504 Project: Hadoop YARN Issue Type: Test

[jira] [Commented] (YARN-3500) Optimize ResourceManager Web loading speed

[ https://issues.apache.org/jira/browse/YARN-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500162#comment-14500162 ] Karthik Kambatla commented on YARN-3500: [~shihaoliang] - do you have a patch in

[jira] [Commented] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501026#comment-14501026 ] Junping Du commented on YARN-3044: -- Thanks [~Naganarasimha] for updating the patch! Looks

[jira] [Commented] (YARN-3474) Add a way to let NM wait RM to come back, not kill running containers

[ https://issues.apache.org/jira/browse/YARN-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501037#comment-14501037 ] Jun Gong commented on YARN-3474: Any comments appreciate. Add a way to let NM wait RM to

[jira] [Commented] (YARN-3463) Integrate OrderingPolicy Framework with CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500937#comment-14500937 ] Jian He commented on YARN-3463: --- - this.schedulableEntities != null can never happen? since

[jira] [Commented] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

[ https://issues.apache.org/jira/browse/YARN-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500940#comment-14500940 ] Jian He commented on YARN-3493: --- TestAMRestart failure unrelated, passing locally. RM fails

[jira] [Updated] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

[ https://issues.apache.org/jira/browse/YARN-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3487: - Summary: CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue (was:

[jira] [Commented] (YARN-3493) RM fails to come up with error Failed to load/recover state when mem settings are changed

[ https://issues.apache.org/jira/browse/YARN-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500946#comment-14500946 ] Hudson commented on YARN-3493: -- SUCCESS: Integrated in Hadoop-trunk-Commit #7609 (See

[jira] [Created] (YARN-3506) Error handling on NM reporting invalid NodeLabels in distributed Node Label configuration

Naganarasimha G R created YARN-3506: --- Summary: Error handling on NM reporting invalid NodeLabels in distributed Node Label configuration Key: YARN-3506 URL: https://issues.apache.org/jira/browse/YARN-3506

[jira] [Commented] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

[ https://issues.apache.org/jira/browse/YARN-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500954#comment-14500954 ] Hudson commented on YARN-3487: -- FAILURE: Integrated in Hadoop-trunk-Commit #7610 (See

[jira] [Commented] (YARN-3504) TestRMRestart fails occasionally in trunk

[ https://issues.apache.org/jira/browse/YARN-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500968#comment-14500968 ] Naganarasimha G R commented on YARN-3504: - seems like duplicate of YARN-2871

[jira] [Commented] (YARN-2740) ResourceManager side should properly handle node label modifications when distributed node label configuration enabled

[ https://issues.apache.org/jira/browse/YARN-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500975#comment-14500975 ] Naganarasimha G R commented on YARN-2740: - Thanks for the comments [~wangda], bq.

[jira] [Updated] (YARN-3431) Sub resources of timeline entity needs to be passed to a separate endpoint.

[ https://issues.apache.org/jira/browse/YARN-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3431: -- Attachment: YARN-3431.4.patch Upload a new patch: 1. Use info to store parent/children relationship. 2.

[jira] [Commented] (YARN-3046) [Event producers] Implement MapReduce AM writing some MR metrics to ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14500998#comment-14500998 ] Zhijie Shen commented on YARN-3046: --- In the new patch, the task entity ID is set

[jira] [Commented] (YARN-3491) PublicLocalizer#addResource is too slow.

[ https://issues.apache.org/jira/browse/YARN-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501002#comment-14501002 ] zhihai xu commented on YARN-3491: - I did more profiling in checkLocalDir. It really

[jira] [Commented] (YARN-3046) [Event producers] Implement MapReduce AM writing some MR metrics to ATS

[ https://issues.apache.org/jira/browse/YARN-3046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14501015#comment-14501015 ] Junping Du commented on YARN-3046: -- bq. In the new patch, the task entity ID is set

<    1   2