[jira] [Commented] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM

[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14733251#comment-14733251 ] Bibin A Chundatt commented on YARN-4106: [~leftnoteasy] Thnks for looking into the issue and

[jira] [Updated] (YARN-2410) Nodemanager ShuffleHandler can possible exhaust file descriptors

[ https://issues.apache.org/jira/browse/YARN-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated YARN-2410: -- Attachment: YARN-2410-v6.patch Thank you so much [~jlowe] for the detailed feedback. I have made all but

[jira] [Commented] (YARN-4120) FSAppAttempt.getResourceUsage() should not take preemptedResource into account

[ https://issues.apache.org/jira/browse/YARN-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14733235#comment-14733235 ] Xianyin Xin commented on YARN-4120: --- Thanks [~kasha]. How about distinguishing getResourceUsage() (the

[jira] [Commented] (YARN-2410) Nodemanager ShuffleHandler can possible exhaust file descriptors

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

[jira] [Created] (YARN-4120) FSAppAttempt.getResourceUsage() should not take preemptedResource into account

Xianyin Xin created YARN-4120: - Summary: FSAppAttempt.getResourceUsage() should not take preemptedResource into account Key: YARN-4120 URL: https://issues.apache.org/jira/browse/YARN-4120 Project: Hadoop

[jira] [Commented] (YARN-4119) Expose the NM bind address as an env, so that AM can make use of it for exposing tracking URL

[ https://issues.apache.org/jira/browse/YARN-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732313#comment-14732313 ] Varun Saxena commented on YARN-4119: This is duplicate of MAPREDUCE-6402 > Expose the NM bind address

[jira] [Updated] (YARN-4121) Typos in capacity scheduler documentation.

[ https://issues.apache.org/jira/browse/YARN-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki updated YARN-4121: - Attachment: YARN-4121.00.patch > Typos in capacity scheduler documentation. >

[jira] [Commented] (YARN-1680) availableResources sent to applicationMaster in heartbeat should exclude blacklistedNodes free memory.

[ https://issues.apache.org/jira/browse/YARN-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732396#comment-14732396 ] Karthik Kambatla commented on YARN-1680: MAPREDUCE-6302 would resolve deadlocks, but only

[jira] [Commented] (YARN-2170) Fix components' version information in the web page 'About the Cluster'

[ https://issues.apache.org/jira/browse/YARN-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732375#comment-14732375 ] Jun Gong commented on YARN-2170: Thanks [~zxu] for the review. > Fix components' version information in

[jira] [Created] (YARN-4121) Typos in capacity scheduler documentation.

Kai Sasaki created YARN-4121: Summary: Typos in capacity scheduler documentation. Key: YARN-4121 URL: https://issues.apache.org/jira/browse/YARN-4121 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-4122) Add support for GPU as a resource

Jun Gong created YARN-4122: -- Summary: Add support for GPU as a resource Key: YARN-4122 URL: https://issues.apache.org/jira/browse/YARN-4122 Project: Hadoop YARN Issue Type: New Feature

[jira] [Commented] (YARN-4120) FSAppAttempt.getResourceUsage() should not take preemptedResource into account

[ https://issues.apache.org/jira/browse/YARN-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732394#comment-14732394 ] Karthik Kambatla commented on YARN-4120: Good catch, [~xinxianyin]. I believe the reason we are

[jira] [Commented] (YARN-4121) Typos in capacity scheduler documentation.

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

[jira] [Commented] (YARN-3446) FairScheduler HeadRoom calculation should exclude nodes in the blacklist.

[ https://issues.apache.org/jira/browse/YARN-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732398#comment-14732398 ] Karthik Kambatla commented on YARN-3446: Discussing the approach on YARN-1680. Let us finalize the

[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again

[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732329#comment-14732329 ] Brahma Reddy Battula commented on YARN-3433: Attached the patch.. Kindly Review.. > Jersey

[jira] [Updated] (YARN-3433) Jersey tests failing with Port in Use -again

[ https://issues.apache.org/jira/browse/YARN-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3433: --- Attachment: YARN-3433.patch > Jersey tests failing with Port in Use -again >

[jira] [Commented] (YARN-3433) Jersey tests failing with Port in Use -again

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

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732430#comment-14732430 ] Karthik Kambatla commented on YARN-2005: In my comments above, if 2.4 shouldn't update the

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14732429#comment-14732429 ] Karthik Kambatla commented on YARN-2005: Thanks for working on this, Anubhav. The approach looks