[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104141#comment-15104141 ] Sunil G commented on YARN-4304: --- Thank you very much Wangda. I also ran test locally and passed the test

[jira] [Commented] (YARN-4557) Few issues in scheduling with Node Labels

[ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104143#comment-15104143 ] Wangda Tan commented on YARN-4557: -- Hi [~Naganarasimha], Thanks for comments, apologize for the delays,

[jira] [Updated] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4108: - Attachment: YARN-4108.poc.3-WIP.patch Attached ver.3 patch, synced to latest trunk, and include end-to-end

[jira] [Commented] (YARN-4557) Few issues in scheduling with Node Labels

[ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104151#comment-15104151 ] Naganarasimha G R commented on YARN-4557: - Thanks for the comments [~wangda], I agree the frequency

[jira] [Commented] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104187#comment-15104187 ] Rohith Sharma K S commented on YARN-4584: - Overall patch looks neat. nits : Test : wait for killed

[jira] [Commented] (YARN-4557) Few issues in scheduling with Node Labels

[ https://issues.apache.org/jira/browse/YARN-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104130#comment-15104130 ] Naganarasimha G R commented on YARN-4557: - Hi [~wangda], Any thoughts on my previous comment ? If

[jira] [Commented] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

[ https://issues.apache.org/jira/browse/YARN-4538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104189#comment-15104189 ] Bibin A Chundatt commented on YARN-4538: Thank you [~rohithsharma],[~sunilg] , [~leftnoteasy] for

[jira] [Commented] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104202#comment-15104202 ] Rohith Sharma K S commented on YARN-4584: - bq. Do we need to deal with these cases? I understand

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104116#comment-15104116 ] Wangda Tan commented on YARN-4304: -- Above failure caused by Jenkins runs build after patch committed. I've

[jira] [Updated] (YARN-4592) Remove unsed GetContainerStatus proto

[ https://issues.apache.org/jira/browse/YARN-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4592: Priority: Trivial (was: Minor) > Remove unsed GetContainerStatus proto >

[jira] [Commented] (YARN-4497) RM might fail to restart when recovering apps whose attempts are missing

[ https://issues.apache.org/jira/browse/YARN-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104225#comment-15104225 ] Rohith Sharma K S commented on YARN-4497: - +1 LGTM, I will wait for couple of days before

[jira] [Updated] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4577: Attachment: YARN-4577.4.patch > Enable aux services to have their own custom classpath/jar file >

[jira] [Commented] (YARN-4577) Enable aux services to have their own custom classpath/jar file

[ https://issues.apache.org/jira/browse/YARN-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104873#comment-15104873 ] Xuan Gong commented on YARN-4577: - Thanks for the comments, [~sjlee0] bq. "how important is it to support

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104893#comment-15104893 ] Wangda Tan commented on YARN-4108: -- Hi [~sunilg], bq. As Wangda mentioned, I think we can discuss this

[jira] [Commented] (YARN-4538) QueueMetrics pending cores and memory metrics wrong

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

[jira] [Commented] (YARN-4502) Fix two AM containers get allocated when AM restart

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

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

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

[jira] [Commented] (YARN-4584) RM startup failure when AM attempts greater than max-attempts

[ https://issues.apache.org/jira/browse/YARN-4584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104158#comment-15104158 ] Jun Gong commented on YARN-4584: [~bibinchundatt] Thanks for the patch. {quote} Remove attempts whose

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104176#comment-15104176 ] Wangda Tan commented on YARN-4304: -- [~sunilg], np, thanks :) > AM max resource configuration per

[jira] [Commented] (YARN-3945) maxApplicationsPerUser is wrongly calculated

[ https://issues.apache.org/jira/browse/YARN-3945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104199#comment-15104199 ] Naganarasimha G R commented on YARN-3945: - Thanks for the comment [~wangda], But the particular

[jira] [Commented] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103964#comment-15103964 ] Junping Du commented on YARN-1480: -- Move it out of 2.6.4 given no update in this JIRA for a long time. >

[jira] [Commented] (YARN-4060) Revisit default retry config for connection with RM

[ https://issues.apache.org/jira/browse/YARN-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103947#comment-15103947 ] Junping Du commented on YARN-4060: -- Hi [~jianhe], do we have plan to deliver a fix in short term? If not,

[jira] [Updated] (YARN-3478) FairScheduler page not performed because different enum of YarnApplicationState and RMAppState

[ https://issues.apache.org/jira/browse/YARN-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3478: - Target Version/s: 2.7.3, 2.6.5 (was: 2.7.3, 2.6.4) > FairScheduler page not performed because different

[jira] [Commented] (YARN-3478) FairScheduler page not performed because different enum of YarnApplicationState and RMAppState

[ https://issues.apache.org/jira/browse/YARN-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103961#comment-15103961 ] Junping Du commented on YARN-3478: -- Move it out of 2.6.4 given no update for a while. > FairScheduler

[jira] [Updated] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1480: - Target Version/s: 2.7.3 (was: 2.7.3, 2.6.4) > RM web services getApps() accepts many more filters than

[jira] [Updated] (YARN-2746) YARNDelegationTokenID misses serializing version from the common abstract ID

[ https://issues.apache.org/jira/browse/YARN-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2746: - Target Version/s: 2.7.3, 2.6.5 (was: 2.7.3, 2.6.4) > YARNDelegationTokenID misses serializing version

[jira] [Commented] (YARN-2457) FairScheduler: Handle preemption to help starved parent queues

[ https://issues.apache.org/jira/browse/YARN-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103954#comment-15103954 ] Junping Du commented on YARN-2457: -- Hi [~ka...@cloudera.com], do we have plan to fix it in short term? If

[jira] [Commented] (YARN-1767) Windows: Allow a way for users to augment classpath of YARN daemons

[ https://issues.apache.org/jira/browse/YARN-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103955#comment-15103955 ] Junping Du commented on YARN-1767: -- Move it to 2.6.5 given no update on this ticket. > Windows: Allow a

[jira] [Updated] (YARN-1767) Windows: Allow a way for users to augment classpath of YARN daemons

[ https://issues.apache.org/jira/browse/YARN-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1767: - Target Version/s: 2.7.3, 2.6.5 (was: 2.7.3, 2.6.4) > Windows: Allow a way for users to augment classpath

[jira] [Commented] (YARN-4265) Provide new timeline plugin storage to support fine-grained entity caching

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

[jira] [Commented] (YARN-1848) Persist ClusterMetrics across RM HA transitions

[ https://issues.apache.org/jira/browse/YARN-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15103986#comment-15103986 ] Junping Du commented on YARN-1848: -- Move it out of 2.6.4 given no update on this JIRA for a while. >

[jira] [Updated] (YARN-1848) Persist ClusterMetrics across RM HA transitions

[ https://issues.apache.org/jira/browse/YARN-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1848: - Target Version/s: 2.7.3, 2.6.5 (was: 2.7.3, 2.6.4) > Persist ClusterMetrics across RM HA transitions >

[jira] [Updated] (YARN-3154) Should not upload partial logs for MR jobs or other "short-running' applications

[ https://issues.apache.org/jira/browse/YARN-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3154: - Fix Version/s: 2.6.4 > Should not upload partial logs for MR jobs or other "short-running' > applications

[jira] [Commented] (YARN-3154) Should not upload partial logs for MR jobs or other "short-running' applications

[ https://issues.apache.org/jira/browse/YARN-3154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15104063#comment-15104063 ] Junping Du commented on YARN-3154: -- I have cherry-pick the commit to branch-2.6. > Should not upload

[jira] [Updated] (YARN-4502) Fix two AM containers get allocated when AM restart

[ https://issues.apache.org/jira/browse/YARN-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4502: - Summary: Fix two AM containers get allocated when AM restart (was: Sometimes Two AM containers get

[jira] [Issue Comment Deleted] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4304: - Comment: was deleted (was: Attached patch fixed test failure.) > AM max resource configuration per

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4304: - Attachment: (was: 0011-YARN-4304.modified.patch) > AM max resource configuration per partition to be

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4304: - Attachment: 0011-YARN-4304.modified.patch Attached patch fixed test failure. > AM max resource

[jira] [Updated] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

[ https://issues.apache.org/jira/browse/YARN-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4304: - Attachment: 0011-YARN-4304.modified.patch Attached patch fixed test failure. > AM max resource

[jira] [Commented] (YARN-4304) AM max resource configuration per partition to be displayed/updated correctly in UI and in various partition related metrics

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