[jira] [Commented] (YARN-5545) App submit failure on queue with label when default queue partition capacity is zero

[ https://issues.apache.org/jira/browse/YARN-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495481#comment-15495481 ] Naganarasimha G R commented on YARN-5545: - Thanks [~sunilg],[~wangda] & [~jlowe], for taking the

[jira] [Commented] (YARN-3140) Improve locks in AbstractCSQueue/LeafQueue/ParentQueue

[ https://issues.apache.org/jira/browse/YARN-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495424#comment-15495424 ] Jian He commented on YARN-3140: --- lgtm, committing in a day if no comments from others. > Improve locks in

[jira] [Commented] (YARN-5545) App submit failure on queue with label when default queue partition capacity is zero

[ https://issues.apache.org/jira/browse/YARN-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495350#comment-15495350 ] Bibin A Chundatt commented on YARN-5545: [~sunilg] {quote} However I think we do not need another

[jira] [Updated] (YARN-5635) Better handling when bad script is configured as Node's HealthScript

[ https://issues.apache.org/jira/browse/YARN-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5635: --- Assignee: (was: Yufei Gu) > Better handling when bad script is configured as Node's HealthScript >

[jira] [Commented] (YARN-5545) App submit failure on queue with label when default queue partition capacity is zero

[ https://issues.apache.org/jira/browse/YARN-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495189#comment-15495189 ] Sunil G commented on YARN-5545: --- Thanks [~jlowe] for the valuable thoughts and suggestions. Thanks

[jira] [Commented] (YARN-5655) TestContainerManagerSecurity is failing

[ https://issues.apache.org/jira/browse/YARN-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495169#comment-15495169 ] Robert Kanter commented on YARN-5655: - This only seems to be a problem in branch-2.8 and branch-2.

[jira] [Commented] (YARN-5545) App submit failure on queue with label when default queue partition capacity is zero

[ https://issues.apache.org/jira/browse/YARN-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495161#comment-15495161 ] Bibin A Chundatt commented on YARN-5545: {quote} Since the maximum-application is major used to cap

[jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495060#comment-15495060 ] Eric Payne commented on YARN-4945: -- [~sunilg], I noticed in the resourcemanager log that the metrics were

[jira] [Commented] (YARN-5642) Typos in 9 log messages

[ https://issues.apache.org/jira/browse/YARN-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495042#comment-15495042 ] Mehran Hassani commented on YARN-5642: -- This means my patch has conflicts with the trunk ? > Typos

[jira] [Commented] (YARN-5642) Typos in 9 log messages

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

[jira] [Updated] (YARN-5642) Typos in 9 log messages

[ https://issues.apache.org/jira/browse/YARN-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehran Hassani updated YARN-5642: - Attachment: YARN-5642.001.patch > Typos in 9 log messages > > >

[jira] [Commented] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494957#comment-15494957 ] Kai Sasaki commented on YARN-5145: -- [~sunilg] I see. Sorry for my misunderstanding and missed the

[jira] [Updated] (YARN-5642) Typos in 9 log messages

[ https://issues.apache.org/jira/browse/YARN-5642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehran Hassani updated YARN-5642: - Summary: Typos in 9 log messages (was: Typos in 11 log messages ) > Typos in 9 log messages >

[jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494825#comment-15494825 ] Wangda Tan commented on YARN-4945: -- 1) YarnConfiguration: - Instead of have a separate

[jira] [Updated] (YARN-5638) Introduce a collector timestamp to uniquely identify collectors creation order in collector discovery

[ https://issues.apache.org/jira/browse/YARN-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-5638: Attachment: YARN-5638-trunk.v1.patch First version of patch to demonstrate the idea. Right now I've split collector

[jira] [Commented] (YARN-3141) Improve locks in SchedulerApplicationAttempt/FSAppAttempt/FiCaSchedulerApp

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

[jira] [Commented] (YARN-5638) Introduce a collector timestamp to uniquely identify collectors creation order in collector discovery

[ https://issues.apache.org/jira/browse/YARN-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494688#comment-15494688 ] Li Lu commented on YARN-5638: - Updated the description of this JIRA. What we need here is not a new type of

[jira] [Updated] (YARN-5638) Introduce a collector timestamp to uniquely identify collectors creation order in collector discovery

[ https://issues.apache.org/jira/browse/YARN-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-5638: Description: As discussed in YARN-3359, we need to further identify timeline collectors' creation order to rebuild

[jira] [Updated] (YARN-5638) Introduce a collector timestamp to uniquely identify collectors creation order in collector discovery

[ https://issues.apache.org/jira/browse/YARN-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-5638: Summary: Introduce a collector timestamp to uniquely identify collectors creation order in collector discovery

[jira] [Updated] (YARN-5336) Put in some limit for accepting key-values in hbase writer

[ https://issues.apache.org/jira/browse/YARN-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-5336: - Assignee: Haibo Chen (was: Vrushali C) > Put in some limit for accepting key-values in hbase writer >

[jira] [Commented] (YARN-5336) Put in some limit for accepting key-values in hbase writer

[ https://issues.apache.org/jira/browse/YARN-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494615#comment-15494615 ] Vrushali C commented on YARN-5336: -- Assigning to [~haibochen] > Put in some limit for accepting

[jira] [Commented] (YARN-5545) App submit failure on queue with label when default queue partition capacity is zero

[ https://issues.apache.org/jira/browse/YARN-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494592#comment-15494592 ] Wangda Tan commented on YARN-5545: -- Thanks [~jlowe], [~sunilg] for suggestions. I generally agree with

[jira] [Updated] (YARN-3141) Improve locks in SchedulerApplicationAttempt/FSAppAttempt/FiCaSchedulerApp

[ https://issues.apache.org/jira/browse/YARN-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3141: - Attachment: YARN-3141.4.patch Attached ver.4 patch. > Improve locks in

[jira] [Commented] (YARN-3141) Improve locks in SchedulerApplicationAttempt/FSAppAttempt/FiCaSchedulerApp

[ https://issues.apache.org/jira/browse/YARN-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494547#comment-15494547 ] Wangda Tan commented on YARN-3141: -- Thanks [~templedf], However I think for most of the comments, we

[jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494454#comment-15494454 ] Wangda Tan commented on YARN-4945: -- [~eepayne], bq. I need to understand what it would mean to combine

[jira] [Commented] (YARN-3692) Allow REST API to set a user generated message when killing an application

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

[jira] [Commented] (YARN-3141) Improve locks in SchedulerApplicationAttempt/FSAppAttempt/FiCaSchedulerApp

[ https://issues.apache.org/jira/browse/YARN-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494440#comment-15494440 ] Daniel Templeton commented on YARN-3141: Continuing with more comments on v2. Sorry, I started

[jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494394#comment-15494394 ] Eric Payne commented on YARN-4945: -- bq. I would say it may not be necessarily to have two separate

[jira] [Commented] (YARN-3140) Improve locks in AbstractCSQueue/LeafQueue/ParentQueue

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

[jira] [Assigned] (YARN-5655) TestContainerManagerSecurity is failing

[ https://issues.apache.org/jira/browse/YARN-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter reassigned YARN-5655: --- Assignee: Robert Kanter Sure. I'll take a look later today. > TestContainerManagerSecurity

[jira] [Commented] (YARN-5655) TestContainerManagerSecurity is failing

[ https://issues.apache.org/jira/browse/YARN-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494375#comment-15494375 ] Jason Lowe commented on YARN-5655: -- git bisect points to this commit when it started failing in

[jira] [Created] (YARN-5655) TestContainerManagerSecurity is failing

Jason Lowe created YARN-5655: Summary: TestContainerManagerSecurity is failing Key: YARN-5655 URL: https://issues.apache.org/jira/browse/YARN-5655 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-3141) Improve locks in SchedulerApplicationAttempt/FSAppAttempt/FiCaSchedulerApp

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

[jira] [Comment Edited] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints

[ https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494251#comment-15494251 ] Varun Saxena edited comment on YARN-5585 at 9/15/16 7:08 PM: - Just to summarise

[jira] [Commented] (YARN-5585) [Atsv2] Add a new filter fromId in REST endpoints

[ https://issues.apache.org/jira/browse/YARN-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494251#comment-15494251 ] Varun Saxena commented on YARN-5585: Just to summarise the suggestions given for folks to refer to. *

[jira] [Commented] (YARN-5545) App submit failure on queue with label when default queue partition capacity is zero

[ https://issues.apache.org/jira/browse/YARN-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494248#comment-15494248 ] Jason Lowe commented on YARN-5545: -- Yes, that's essentially the idea. Users can work around the issue

[jira] [Resolved] (YARN-5640) Issue while accessing resource manager webapp rest service

[ https://issues.apache.org/jira/browse/YARN-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Loknath Priyatham Teja Singamsetty resolved YARN-5640. --- Resolution: Not A Bug > Issue while accessing resource

[jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494187#comment-15494187 ] Wangda Tan commented on YARN-4945: -- [~eepayne] / [~sunilg], For the suggestion from [~eepayne]: bq. I

[jira] [Commented] (YARN-3140) Improve locks in AbstractCSQueue/LeafQueue/ParentQueue

[ https://issues.apache.org/jira/browse/YARN-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494172#comment-15494172 ] Wangda Tan commented on YARN-3140: -- Thanks [~jianhe] for review, Addressed all comments, except: bq.

[jira] [Updated] (YARN-3140) Improve locks in AbstractCSQueue/LeafQueue/ParentQueue

[ https://issues.apache.org/jira/browse/YARN-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3140: - Attachment: YARN-3140.3.patch > Improve locks in AbstractCSQueue/LeafQueue/ParentQueue >

[jira] [Updated] (YARN-3141) Improve locks in SchedulerApplicationAttempt/FSAppAttempt/FiCaSchedulerApp

[ https://issues.apache.org/jira/browse/YARN-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3141: - Attachment: YARN-3141.3.patch > Improve locks in SchedulerApplicationAttempt/FSAppAttempt/FiCaSchedulerApp

[jira] [Commented] (YARN-3141) Improve locks in SchedulerApplicationAttempt/FSAppAttempt/FiCaSchedulerApp

[ https://issues.apache.org/jira/browse/YARN-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494159#comment-15494159 ] Wangda Tan commented on YARN-3141: -- Thanks for review, [~templedf], I addressed all your suggestions

[jira] [Commented] (YARN-5545) App submit failure on queue with label when default queue partition capacity is zero

[ https://issues.apache.org/jira/browse/YARN-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494147#comment-15494147 ] Sunil G commented on YARN-5545: --- Thank you very much [~jlowe] for sharing use case and detailed analysis. I

[jira] [Commented] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494121#comment-15494121 ] Sunil G commented on YARN-5145: --- As per below doc, {{under

[jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494103#comment-15494103 ] Sunil G commented on YARN-4945: --- I think i missed the previous comment from [~eepayne]. Let me share another

[jira] [Updated] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4945: -- Attachment: YARN-2009.v2.patch Attaching v2 patch addressing the mentioned todo's. [~leftnoteasy] and

[jira] [Commented] (YARN-5637) Changes in NodeManager to support Container upgrade and rollback/commit

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

[jira] [Commented] (YARN-4329) Allow fetching exact reason as to why a submitted app is in ACCEPTED state in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493961#comment-15493961 ] Yufei Gu commented on YARN-4329: Thanks [~Naganarasimha]! I found you've done basic framework in YARN-3946.

[jira] [Updated] (YARN-5637) Changes in NodeManager to support Container upgrade and rollback/commit

[ https://issues.apache.org/jira/browse/YARN-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5637: -- Attachment: YARN-5637.005.patch Fixing checkstyle, javadocs and tests > Changes in NodeManager to

[jira] [Commented] (YARN-5637) Changes in NodeManager to support Container upgrade and rollback/commit

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

[jira] [Updated] (YARN-3692) Allow REST API to set a user generated message when killing an application

[ https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3692: Attachment: 0005-YARN-3692.1.patch Removed unused import and updated the patch > Allow REST

[jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493893#comment-15493893 ] Eric Payne commented on YARN-4945: -- Thanks again, [~sunilg]. I will look closely at the patch, but one

[jira] [Commented] (YARN-3692) Allow REST API to set a user generated message when killing an application

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

[jira] [Updated] (YARN-5637) Changes in NodeManager to support Container upgrade and rollback/commit

[ https://issues.apache.org/jira/browse/YARN-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5637: -- Attachment: YARN-5637.004.patch Rebasing patch with latest YARN-5620 > Changes in NodeManager to

[jira] [Commented] (YARN-5577) [Atsv2] Document object passing in infofilters with an example

[ https://issues.apache.org/jira/browse/YARN-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493714#comment-15493714 ] Rohith Sharma K S commented on YARN-5577: - ping [~varun_saxena]!! > [Atsv2] Document object

[jira] [Comment Edited] (YARN-5620) Core changes in NodeManager to support re-initialization of Containers with new launchContext

[ https://issues.apache.org/jira/browse/YARN-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493609#comment-15493609 ] Arun Suresh edited comment on YARN-5620 at 9/15/16 3:13 PM: Committed this to

[jira] [Commented] (YARN-5620) Core changes in NodeManager to support re-initialization of Containers with new launchContext

[ https://issues.apache.org/jira/browse/YARN-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493609#comment-15493609 ] Arun Suresh commented on YARN-5620: --- Committed this to trunk and branch-2 > Core changes in NodeManager

[jira] [Updated] (YARN-5620) Core changes in NodeManager to support re-initialization of Containers with new launchContext

[ https://issues.apache.org/jira/browse/YARN-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5620: -- Fix Version/s: 3.0.0-alpha2 2.9.0 > Core changes in NodeManager to support

[jira] [Commented] (YARN-5620) Core changes in NodeManager to support re-initialization of Containers with new launchContext

[ https://issues.apache.org/jira/browse/YARN-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493503#comment-15493503 ] Hudson commented on YARN-5620: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #10443 (See

[jira] [Commented] (YARN-5620) Core changes in NodeManager to support re-initialization of Containers with new launchContext

[ https://issues.apache.org/jira/browse/YARN-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493431#comment-15493431 ] Arun Suresh commented on YARN-5620: --- Committing this shortly based on [~vvasudev]'s and [~jianhe]'s +1.

[jira] [Commented] (YARN-5620) Core changes in NodeManager to support re-initialization of Containers with new launchContext

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

[jira] [Commented] (YARN-5631) Missing refreshClusterMaxPriority usage in rmadmin help message

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

[jira] [Updated] (YARN-5620) Core changes in NodeManager to support re-initialization of Containers with new launchContext

[ https://issues.apache.org/jira/browse/YARN-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5620: -- Attachment: YARN-5620.016.patch Thanks for the review [~vvasudev].. Uploading final patch with the

[jira] [Commented] (YARN-5545) App submit failure on queue with label when default queue partition capacity is zero

[ https://issues.apache.org/jira/browse/YARN-5545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493271#comment-15493271 ] Jason Lowe commented on YARN-5545: -- bq. This could be configured to set max-apps per queue level in

[jira] [Updated] (YARN-3692) Allow REST API to set a user generated message when killing an application

[ https://issues.apache.org/jira/browse/YARN-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3692: Attachment: 0005-YARN-3692.patch Updated the patch addressing review comments. > Allow

[jira] [Updated] (YARN-5631) Missing refreshClusterMaxPriority usage in rmadmin help message

[ https://issues.apache.org/jira/browse/YARN-5631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki updated YARN-5631: - Attachment: YARN-5631-branch-2.8.02.patch > Missing refreshClusterMaxPriority usage in rmadmin help

[jira] [Commented] (YARN-3140) Improve locks in AbstractCSQueue/LeafQueue/ParentQueue

[ https://issues.apache.org/jira/browse/YARN-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493012#comment-15493012 ] Jian He commented on YARN-3140: --- - Is this method not used ? If so, labelManager no need to be volatile, and

[jira] [Commented] (YARN-5145) [YARN-3368] Move new YARN UI configuration to HADOOP_CONF_DIR

[ https://issues.apache.org/jira/browse/YARN-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493000#comment-15493000 ] Kai Sasaki commented on YARN-5145: -- [~sunilg] Sorry for lacking of explanation. It seems that

[jira] [Commented] (YARN-5620) Core changes in NodeManager to support re-initialization of Containers with new launchContext

[ https://issues.apache.org/jira/browse/YARN-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492925#comment-15492925 ] Varun Vasudev commented on YARN-5620: - Thanks for the patch [~asuresh]. +1 except for some minor

[jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue

[ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492609#comment-15492609 ] Wangda Tan commented on YARN-4945: -- [~sunilg], took a quick look at the patch, overall approach looks

[jira] [Commented] (YARN-4329) Allow fetching exact reason as to why a submitted app is in ACCEPTED state in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15492585#comment-15492585 ] Naganarasimha G R commented on YARN-4329: - Thanks [~yufeigu] for working on this! As i am not much

[jira] [Commented] (YARN-5631) Missing refreshClusterMaxPriority usage in rmadmin help message

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