[jira] [Commented] (YARN-4654) Yarn node label CLI should parse "=" correctly when trying to remove all labels on a node

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

[jira] [Commented] (YARN-4654) Yarn node label CLI should parse "=" correctly when trying to remove all labels on a node

[ https://issues.apache.org/jira/browse/YARN-4654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152101#comment-15152101 ] Naganarasimha G R commented on YARN-4654: - Thanks for the review and commit [~rohithsharma] &

[jira] [Commented] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token

[ https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152105#comment-15152105 ] Naganarasimha G R commented on YARN-4183: - Hi [~sjlee0] & [~jeagles], Any further reviews /

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152148#comment-15152148 ] Steve Loughran commented on YARN-4696: -- # forgot about the -default.xml; will fix # anyone overrriding

[jira] [Updated] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4696: - Attachment: YARN-4696-003.patch Patch -003 Addresses # discussion # checkstyle # javadocs Adds a

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

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

[jira] [Created] (YARN-4703) blacklist option for distributedshell

kyungwan nam created YARN-4703: -- Summary: blacklist option for distributedshell Key: YARN-4703 URL: https://issues.apache.org/jira/browse/YARN-4703 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-4703) blacklist option for distributedshell

[ https://issues.apache.org/jira/browse/YARN-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-4703: --- Attachment: YARN-4703.001.patch I attached a patch including test code. > blacklist option for

[jira] [Commented] (YARN-3934) Application with large ApplicationSubmissionContext can cause RM to exit when ZK store is used

[ https://issues.apache.org/jira/browse/YARN-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152283#comment-15152283 ] Dustin Cote commented on YARN-3934: --- [~mingma] can you have a look at the proposed patch and let me know

[jira] [Commented] (YARN-4333) Fair scheduler should support preemption within queue

[ https://issues.apache.org/jira/browse/YARN-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152594#comment-15152594 ] Tao Jie commented on YARN-4333: --- [~kasha], Thank you for reply! I just took a look at YARN-3405 thanks to

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152656#comment-15152656 ] Steve Loughran commented on YARN-4696: -- Patch -003. Adds more robustness/diagnostics to the plugin

[jira] [Updated] (YARN-4675) Reorganize TimeClientImpl into TimeClientV1Impl and TimeClientV2Impl

[ https://issues.apache.org/jira/browse/YARN-4675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4675: Attachment: YARN-4675-YARN-2928.v1.001.patch I have refactored the TimelineClientImpl &

[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=15152729#comment-15152729 ] Naganarasimha G R commented on YARN-3945: - Thanks for the clarification [~wangda], Yes it would be

[jira] [Commented] (YARN-4692) [Umbrella] Simplified and first-class support for services in YARN

[ https://issues.apache.org/jira/browse/YARN-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152735#comment-15152735 ] Arun Suresh commented on YARN-4692: --- [~leftnoteasy], Am not entirely convinced that Priorities will

[jira] [Commented] (YARN-3215) Respect labels in CapacityScheduler when computing headroom

[ https://issues.apache.org/jira/browse/YARN-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152734#comment-15152734 ] Naganarasimha G R commented on YARN-3215: - Hi [~steve_l] / [~wangda], Any updates on this wrt to

[jira] [Commented] (YARN-4675) Reorganize TimeClientImpl into TimeClientV1Impl and TimeClientV2Impl

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

[jira] [Commented] (YARN-4634) Scheduler UI/Metrics need to consider cases like non-queue label mappings

[ https://issues.apache.org/jira/browse/YARN-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152800#comment-15152800 ] Sunil G commented on YARN-4634: --- Hi [~leftnoteasy] Yes, I understood the scenario which you have mentioned.

[jira] [Commented] (YARN-4634) Scheduler UI/Metrics need to consider cases like non-queue label mappings

[ https://issues.apache.org/jira/browse/YARN-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152827#comment-15152827 ] Wangda Tan commented on YARN-4634: -- [~sunilg], My understanding of your proposal is, we will show

[jira] [Commented] (YARN-4696) EntityGroupFSTimelineStore to work in the absence of an RM

[ https://issues.apache.org/jira/browse/YARN-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152923#comment-15152923 ] Li Lu commented on YARN-4696: - Thanks [~ste...@apache.org]! The latest patch LGTM. Could some committers have

[jira] [Updated] (YARN-4412) Create ClusterMonitor to compute ordered list of preferred NMs for OPPORTUNITIC containers

[ https://issues.apache.org/jira/browse/YARN-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4412: -- Attachment: YARN-4412-yarn-2877.v5.patch Updating patch to add some more documentation.. > Create

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

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

[jira] [Commented] (YARN-4412) Create ClusterMonitor to compute ordered list of preferred NMs for OPPORTUNITIC containers

[ https://issues.apache.org/jira/browse/YARN-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15152964#comment-15152964 ] Carlo Curino commented on YARN-4412: [~asuresh], thanks for addressing my concerns and adding

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Attachment: yarn4701.001.patch > When task logs are not available, port 8041 is referenced instead of port

[jira] [Updated] (YARN-3344) procfs stat file is not in the expected format warning

[ https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-3344: Attachment: YARN-3344.06.patch > procfs stat file is not in the expected format warning >

[jira] [Assigned] (YARN-3344) procfs stat file is not in the expected format warning

[ https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA reassigned YARN-3344: --- Assignee: Akira AJISAKA (was: Ravindra Kumar Naik) > procfs stat file is not in the expected

[jira] [Updated] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Zhi updated YARN-4676: - Attachment: HADOOP-4676.006.patch > Automatic and Asynchronous Decommissioning Nodes Status Tracking >

[jira] [Commented] (YARN-3344) procfs stat file is not in the expected format warning

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

[jira] [Created] (YARN-4704) TestResourceManager#testResourceAllocation() fails when using FairScheduler

Ray Chiang created YARN-4704: Summary: TestResourceManager#testResourceAllocation() fails when using FairScheduler Key: YARN-4704 URL: https://issues.apache.org/jira/browse/YARN-4704 Project: Hadoop YARN

[jira] [Updated] (YARN-4412) Create ClusterMonitor to compute ordered list of preferred NMs for OPPORTUNITIC containers

[ https://issues.apache.org/jira/browse/YARN-4412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-4412: -- Attachment: YARN-4412-yarn-2877.v6.patch > Create ClusterMonitor to compute ordered list of preferred

[jira] [Commented] (YARN-4412) Create ClusterMonitor to compute ordered list of preferred NMs for OPPORTUNITIC containers

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

[jira] [Commented] (YARN-4692) [Umbrella] Simplified and first-class support for services in YARN

[ https://issues.apache.org/jira/browse/YARN-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153434#comment-15153434 ] Wangda Tan commented on YARN-4692: -- [~asuresh], Thanks for reply, I can understand your concern now.

[jira] [Updated] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-4701: - Description: Accessing logs for an task attempt in the workflow tool in Hue shows "Logs not available for

[jira] [Commented] (YARN-4701) When task logs are not available, port 8041 is referenced instead of port 8042

[ https://issues.apache.org/jira/browse/YARN-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153519#comment-15153519 ] Robert Kanter commented on YARN-4701: - A few comments: - When {{getApplicationLogURL()}} returns null,

[jira] [Commented] (YARN-4545) Allow YARN distributed shell to use ATS v1.5 APIs

[ https://issues.apache.org/jira/browse/YARN-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153542#comment-15153542 ] Li Lu commented on YARN-4545: - Thanks [~ste...@apache.org]! bq. the new

[jira] [Updated] (YARN-4678) Cluster used capacity is > 100 when container reserved

[ https://issues.apache.org/jira/browse/YARN-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-4678: --- Assignee: Sunil G (was: Brahma Reddy Battula) > Cluster used capacity is > 100 when

[jira] [Commented] (YARN-4678) Cluster used capacity is > 100 when container reserved

[ https://issues.apache.org/jira/browse/YARN-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153547#comment-15153547 ] Brahma Reddy Battula commented on YARN-4678: [~sunilg] thanks for the patch..Approach looks

[jira] [Commented] (YARN-4412) Create ClusterMonitor to compute ordered list of preferred NMs for OPPORTUNITIC containers

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

[jira] [Commented] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

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

[jira] [Updated] (YARN-4703) blacklist option for distributedshell

[ https://issues.apache.org/jira/browse/YARN-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-4703: --- Attachment: YARN-4703.001.patch > blacklist option for distributedshell >

[jira] [Updated] (YARN-4703) blacklist option for distributedshell

[ https://issues.apache.org/jira/browse/YARN-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-4703: --- Attachment: (was: YARN-4703.001.patch) > blacklist option for distributedshell >

[jira] [Commented] (YARN-4703) blacklist option for distributedshell

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

[jira] [Commented] (YARN-4697) NM aggregation thread pool is not bound by limits

[ https://issues.apache.org/jira/browse/YARN-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15153675#comment-15153675 ] Wilfred Spiegelenburg commented on YARN-4697: - [~haibochen] should we do some range checking on