[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

[ https://issues.apache.org/jira/browse/YARN-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520484#comment-14520484 ] Zhijie Shen commented on YARN-3551: --- Cool, thanks for the comments, Sangjin. So the

[jira] [Commented] (YARN-3477) TimelineClientImpl swallows exceptions

[ https://issues.apache.org/jira/browse/YARN-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520560#comment-14520560 ] Zhijie Shen commented on YARN-3477: --- +1 for unwrap the failing exception. Some thoughts

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

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

[jira] [Commented] (YARN-3535) ResourceRequest should be restored back to scheduler when RMContainer is killed at ALLOCATED

[ https://issues.apache.org/jira/browse/YARN-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14519368#comment-14519368 ] Peng Zhang commented on YARN-3535: -- I think TestAMRestart failure is not related with this

[jira] [Commented] (YARN-3554) Default value for maximum nodemanager connect wait time is too high

[ https://issues.apache.org/jira/browse/YARN-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14519360#comment-14519360 ] Jason Lowe commented on YARN-3554: -- I think 10 minutes is still too high. We didn't even

[jira] [Commented] (YARN-3445) Cache runningApps in RMNode for getting running apps on given NodeId

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

[jira] [Updated] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

[ https://issues.apache.org/jira/browse/YARN-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2619: Attachment: YARN-2619.004.patch bq. there is an unused import

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

[ https://issues.apache.org/jira/browse/YARN-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14519342#comment-14519342 ] Varun Vasudev commented on YARN-2619: - The sharing is just an equal split of disk

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

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

[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=14519471#comment-14519471 ] Junping Du commented on YARN-3044: -- bq. l.179: curious, we could add them to the entity as

[jira] [Commented] (YARN-3517) RM web ui for dumping scheduler logs should be for admins only

[ https://issues.apache.org/jira/browse/YARN-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14519423#comment-14519423 ] Varun Vasudev commented on YARN-3517: - The test failure is unrelated to the patch. RM

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

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

[jira] [Commented] (YARN-3546) AbstractYarnScheduler.getApplicationAttempt seems misleading, and there're some misuse of it

[ https://issues.apache.org/jira/browse/YARN-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520706#comment-14520706 ] sandflee commented on YARN-3546: [~jianhe], thanks for your explanation, I stil have one

[jira] [Commented] (YARN-3546) AbstractYarnScheduler.getApplicationAttempt seems misleading, and there're some misuse of it

[ https://issues.apache.org/jira/browse/YARN-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520742#comment-14520742 ] Jian He commented on YARN-3546: --- Didn't get you. the waitForSchedulerAppAttemptAdded

[jira] [Commented] (YARN-3534) Report node resource utilization

[ https://issues.apache.org/jira/browse/YARN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520604#comment-14520604 ] Karthik Kambatla commented on YARN-3534: Thanks for pointing me to YARN-3481,

[jira] [Commented] (YARN-3565) NodeHeartbeatRequest/RegisterNodeManagerRequest should use NodeLabel object instead of String

[ https://issues.apache.org/jira/browse/YARN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520672#comment-14520672 ] Naganarasimha G R commented on YARN-3565: - Hi [~wangda], I would like to work on

[jira] [Assigned] (YARN-3565) NodeHeartbeatRequest/RegisterNodeManagerRequest should use NodeLabel object instead of String

[ https://issues.apache.org/jira/browse/YARN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R reassigned YARN-3565: --- Assignee: Naganarasimha G R (was: Wangda Tan)

[jira] [Commented] (YARN-3544) AM logs link missing in the RM UI for a completed app

[ https://issues.apache.org/jira/browse/YARN-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520663#comment-14520663 ] Xuan Gong commented on YARN-3544: - bq. the patch doesn't apply for branch-2.7. It seems to

[jira] [Updated] (YARN-3544) AM logs link missing in the RM UI for a completed app

[ https://issues.apache.org/jira/browse/YARN-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3544: Attachment: YARN-3544-branch-2.7-1.patch AM logs link missing in the RM UI for a completed app

[jira] [Commented] (YARN-3563) Completed app shows -1 running containers on RM web UI

[ https://issues.apache.org/jira/browse/YARN-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520666#comment-14520666 ] Rohith commented on YARN-3563: -- From the screenshot attached, I confirm that it should be

[jira] [Commented] (YARN-3544) AM logs link missing in the RM UI for a completed app

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

[jira] [Created] (YARN-3561) Non-AM Containers continue to run even after AM is stopped

Gour Saha created YARN-3561: --- Summary: Non-AM Containers continue to run even after AM is stopped Key: YARN-3561 URL: https://issues.apache.org/jira/browse/YARN-3561 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-3045) [Event producers] Implement NM writing container lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520902#comment-14520902 ] Naganarasimha G R commented on YARN-3045: - Thanks for the reviews [~sjlee0]

[jira] [Commented] (YARN-3484) Fix up yarn top shell code

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

[jira] [Commented] (YARN-3544) AM logs link missing in the RM UI for a completed app

[ https://issues.apache.org/jira/browse/YARN-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520859#comment-14520859 ] Zhijie Shen commented on YARN-3544: --- Thanks for creating the branch-2.7 patch. One nit:

[jira] [Updated] (YARN-3271) FairScheduler: Move tests related to max-runnable-apps from TestFairScheduler to TestAppRunnability

[ https://issues.apache.org/jira/browse/YARN-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3271: Attachment: YARN-3271.2.patch thanks [~kasha] for the comments Updated patch as per your comment. Please review

[jira] [Updated] (YARN-3552) RM Web UI display negative number for running containers

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3552: - Summary: RM Web UI display negative number for running containers (was:

[jira] [Resolved] (YARN-3563) Completed app shows -1 running containers on RM web UI

[ https://issues.apache.org/jira/browse/YARN-3563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-3563. --- Resolution: Duplicate Didn't notice YARN-3563. Close this one as a duplicate Completed app shows -1

[jira] [Commented] (YARN-2893) AMLaucher: sporadic job failures due to EOFException in readTokenStorageStream

[ https://issues.apache.org/jira/browse/YARN-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520879#comment-14520879 ] Gera Shegalov commented on YARN-2893: - Hi [~zxu], thanks for updating the patch. I

[jira] [Updated] (YARN-3552) RM Web UI display negative number for running containers

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3552: - Attachment: 0001-YARN-3552.patch RM Web UI display negative number for running containers

[jira] [Updated] (YARN-3552) RM Web UI shows -1 running containers for completed apps

[ https://issues.apache.org/jira/browse/YARN-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-3552: - Summary: RM Web UI shows -1 running containers for completed apps (was: RM Web UI display negative number for

[jira] [Commented] (YARN-3045) [Event producers] Implement NM writing container lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520782#comment-14520782 ] Naganarasimha G R commented on YARN-3045: - Hi [~sjlee0], I have modeled it

[jira] [Commented] (YARN-3546) AbstractYarnScheduler.getApplicationAttempt seems misleading, and there're some misuse of it

[ https://issues.apache.org/jira/browse/YARN-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520819#comment-14520819 ] sandflee commented on YARN-3546: sorry for my explanation. Let's consider below situation,

[jira] [Commented] (YARN-3481) Report NM aggregated container resource utilization in heartbeat

[ https://issues.apache.org/jira/browse/YARN-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520825#comment-14520825 ] Vinod Kumar Vavilapalli commented on YARN-3481: --- Sorry, didn't realize

[jira] [Commented] (YARN-3534) Report node resource utilization

[ https://issues.apache.org/jira/browse/YARN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520829#comment-14520829 ] Vinod Kumar Vavilapalli commented on YARN-3534: --- Please see my comment [on

[jira] [Commented] (YARN-3366) Outbound network bandwidth : classify/shape traffic originating from YARN containers

[ https://issues.apache.org/jira/browse/YARN-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520788#comment-14520788 ] Jun Gong commented on YARN-3366: When addYARNRootClass in

[jira] [Commented] (YARN-3045) [Event producers] Implement NM writing container lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520810#comment-14520810 ] Sangjin Lee commented on YARN-3045: --- I'm not good at it either. :) My basic idea is, if

[jira] [Commented] (YARN-3546) AbstractYarnScheduler.getApplicationAttempt seems misleading, and there're some misuse of it

[ https://issues.apache.org/jira/browse/YARN-3546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520838#comment-14520838 ] sandflee commented on YARN-3546: The implement of

[jira] [Commented] (YARN-3045) [Event producers] Implement NM writing container lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14520843#comment-14520843 ] Vinod Kumar Vavilapalli commented on YARN-3045: --- The allocated

[jira] [Commented] (YARN-3485) FairScheduler headroom calculation doesn't consider maxResources for Fifo and FairShare policies

[ https://issues.apache.org/jira/browse/YARN-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14519526#comment-14519526 ] Hudson commented on YARN-3485: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #179 (See

<    1   2