[jira] [Commented] (YARN-1051) YARN Admission Control/Planner: enhancing the resource allocation model with time.

[ https://issues.apache.org/jira/browse/YARN-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140910#comment-15140910 ] Lei Guo commented on YARN-1051: --- [~curino], for enterprise customer, the scheduling policy will be

[jira] [Commented] (YARN-4655) Log uncaught exceptions/errors in various thread pools in the nodemanger

[ https://issues.apache.org/jira/browse/YARN-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140991#comment-15140991 ] Varun Vasudev commented on YARN-4655: - +1. I'll commit this tomorrow if no one objects. > Log uncaught

[jira] [Updated] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-4653: - Attachment: YARN-4653-004.patch Patch 004; write down my understanding of AM token renewal (based

[jira] [Commented] (YARN-4653) Document YARN security model from the perspective of Application Developers

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

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140973#comment-15140973 ] Jian He commented on YARN-4138: --- patch looks good to me, [~sandflee], do you have any more comments ? > Roll

[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=15141241#comment-15141241 ] Arun Suresh commented on YARN-4412: --- [~curino], is it possible to give this a review ? > Create

[jira] [Commented] (YARN-1051) YARN Admission Control/Planner: enhancing the resource allocation model with time.

[ https://issues.apache.org/jira/browse/YARN-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141266#comment-15141266 ] Carlo Curino commented on YARN-1051: [~grey], I suggest you to read the attached techreport for full

[jira] [Commented] (YARN-2885) Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers

[ https://issues.apache.org/jira/browse/YARN-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141190#comment-15141190 ] Carlo Curino commented on YARN-2885: Cool. Just to be explicit about it I am +1 on committing this to

[jira] [Commented] (YARN-4360) Improve GreedyReservationAgent to support "early" allocations, and performance improvements

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

[jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141162#comment-15141162 ] Prabhu Joseph commented on YARN-4682: - [~ste...@apache.org] Steve, do i need to checkout branch-2.

[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=15141349#comment-15141349 ] Carlo Curino commented on YARN-4412: Hi [~asuresh], I really like the direction of the patch. I had

[jira] [Commented] (YARN-4420) Add REST API for List Reservations

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

[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=15141444#comment-15141444 ] Naganarasimha G R commented on YARN-4183: - Hi [~jeagles] & [~mitdesai], Any thoughts on the

[jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141304#comment-15141304 ] Steve Loughran commented on YARN-4682: -- to get a patch we can put into Hadoop, yes, you need to check

[jira] [Commented] (YARN-4360) Improve GreedyReservationAgent to support "early" allocations, and performance improvements

[ https://issues.apache.org/jira/browse/YARN-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141355#comment-15141355 ] Carlo Curino commented on YARN-4360: [~asuresh], thanks so much for the reviews and commit. > Improve

[jira] [Updated] (YARN-4628) TopCli to support Application priority

[ https://issues.apache.org/jira/browse/YARN-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4628: --- Attachment: 0003-YARN-4628.patch [~sunilg] Thanks for review comment. By default if we are

[jira] [Commented] (YARN-4628) TopCli to support Application priority

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

[jira] [Updated] (YARN-2575) Consider creating separate ACLs for Reservation create/update/delete/list ops

[ https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Po updated YARN-2575: -- Attachment: YARN-2575.v11.patch Thanks [~asuresh] for the comments. I added your comments to patch

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141736#comment-15141736 ] Eric Badger commented on YARN-4686: --- Moving to YARN project, since this affects the MiniYarnCluster. >

[jira] [Moved] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger moved MAPREDUCE-6507 to YARN-4686: -- Assignee: (was: Eric Badger) Target Version/s: 2.7.3

[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=15141869#comment-15141869 ] Hadoop QA commented on YARN-4676: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[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: graceful-decommission-v2.patch > Automatic and Asynchronous Decommissioning Nodes Status

[jira] [Commented] (YARN-4420) Add REST API for List Reservations

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

[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: (was: graceful-decommission-v1.patch) > Automatic and Asynchronous Decommissioning Nodes

[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: (was: graceful-decommission-v0.patch) > Automatic and Asynchronous Decommissioning Nodes

[jira] [Commented] (YARN-4420) Add REST API for List Reservations

[ https://issues.apache.org/jira/browse/YARN-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141862#comment-15141862 ] Carlo Curino commented on YARN-4420: Thanks [~seanpo03], I committed this to trunk, branch-2, and

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142052#comment-15142052 ] sandflee commented on YARN-4138: looks good to me too, thanks [~mding] > Roll back container resource

[jira] [Updated] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-4682: Attachment: YARN-4682.patch.1 > AMRM client to log when AMRM token updated >

[jira] [Comment Edited] (YARN-4628) Display application priority in yarn top

[ https://issues.apache.org/jira/browse/YARN-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142308#comment-15142308 ] Varun Vasudev edited comment on YARN-4628 at 2/11/16 6:32 AM: -- +1. Committed

[jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated

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

[jira] [Commented] (YARN-4655) Log uncaught exceptions/errors in various thread pools in YARN

[ https://issues.apache.org/jira/browse/YARN-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142345#comment-15142345 ] Sidharta Seethana commented on YARN-4655: - Thanks, [~vvasudev]. > Log uncaught exceptions/errors

[jira] [Updated] (YARN-4628) Display application priority in yarn top

[ https://issues.apache.org/jira/browse/YARN-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4628: Summary: Display application priority in yarn top (was: TopCli to support Application priority ) >

[jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142301#comment-15142301 ] Prabhu Joseph commented on YARN-4682: - git checkout branch-2 git diff > YARN-4682.patch.1 But I am not

[jira] [Commented] (YARN-4655) Log uncaught exceptions/errors in various thread pools in YARN

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

[jira] [Commented] (YARN-4628) Display application priority in yarn top

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

[jira] [Commented] (YARN-2885) Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers

[ https://issues.apache.org/jira/browse/YARN-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142346#comment-15142346 ] Arun Suresh commented on YARN-2885: --- Thanks [~curino], [~leftnoteasy], [~kishorch], [~kkaranasos] and

[jira] [Updated] (YARN-4655) Log uncaught exceptions/errors in various thread pools in YARN

[ https://issues.apache.org/jira/browse/YARN-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4655: Issue Type: Improvement (was: Bug) > Log uncaught exceptions/errors in various thread pools in YARN

[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=15142338#comment-15142338 ] Hadoop QA commented on YARN-4676: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-4681) ProcfsBasedProcessTree should not calculate private clean pages

[ https://issues.apache.org/jira/browse/YARN-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Lukavsky updated YARN-4681: --- Attachment: YARN-4681.patch Added backward compatibility, removed some warnings. >

[jira] [Updated] (YARN-4685) AM blacklisting result in application to get hanged

[ https://issues.apache.org/jira/browse/YARN-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4685: Summary: AM blacklisting result in application to get hanged (was: AM blacklist

[jira] [Updated] (YARN-4685) AM blacklist addition/removal should get updated for every allocate call from RMAppAttemptImpl.

[ https://issues.apache.org/jira/browse/YARN-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4685: Priority: Major (was: Blocker) > AM blacklist addition/removal should get updated for every

[jira] [Updated] (YARN-4685) AM blacklist addition/removal should get updated for every allocate call from RMAppAttemptImpl.

[ https://issues.apache.org/jira/browse/YARN-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4685: Description: AM blacklist addition or removal is updated only when RMAppAttempt is scheduled

[jira] [Commented] (YARN-4684) TestYarnCLI#testGetContainers failing in trunk

[ https://issues.apache.org/jira/browse/YARN-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140508#comment-15140508 ] Bibin A Chundatt commented on YARN-4684: All testcase failures are already tracked as part for

[jira] [Commented] (YARN-4681) ProcfsBasedProcessTree should not calculate private clean pages

[ https://issues.apache.org/jira/browse/YARN-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140515#comment-15140515 ] Jan Lukavsky commented on YARN-4681: [~cnauroth], I tested this patch against our jobs and it kind of

[jira] [Commented] (YARN-4685) AM blacklist addition/removal should get updated for every allocate call from RMAppAttemptImpl.

[ https://issues.apache.org/jira/browse/YARN-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140512#comment-15140512 ] Rohith Sharma K S commented on YARN-4685: - Currently RMAppAttemptImpl start calling allocate method

[jira] [Commented] (YARN-4685) AM blacklist addition/removal should get updated for every allocate call from RMAppAttemptImpl.

[ https://issues.apache.org/jira/browse/YARN-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140526#comment-15140526 ] Rohith Sharma K S commented on YARN-4685: - One of the case where application got stuck is # Cluster

[jira] [Updated] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-4682: Attachment: YARN-4682.patch > AMRM client to log when AMRM token updated >

[jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140720#comment-15140720 ] Prabhu Joseph commented on YARN-4682: - [~ste...@apache.org] Added a info log. > AMRM client to log

[jira] [Commented] (YARN-4629) Distributed shell breaks under strong security

[ https://issues.apache.org/jira/browse/YARN-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140729#comment-15140729 ] Steve Loughran commented on YARN-4629: -- +1 I've already been testing a variant of this in slider; in

[jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated

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

[jira] [Commented] (YARN-4653) Document YARN security model from the perspective of Application Developers

[ https://issues.apache.org/jira/browse/YARN-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140742#comment-15140742 ] Steve Loughran commented on YARN-4653: -- ok, to confirm then # the token handed off by the RM to the

[jira] [Commented] (YARN-4629) Distributed shell breaks under strong security

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

[jira] [Commented] (YARN-4682) AMRM client to log when AMRM token updated

[ https://issues.apache.org/jira/browse/YARN-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15140754#comment-15140754 ] Steve Loughran commented on YARN-4682: -- Prabhu, the patch isn't applying as it's against an old

[jira] [Updated] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4519: -- Fix Version/s: (was: 2.9.0) 2.8.0 > potential deadlock of CapacityScheduler between

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142158#comment-15142158 ] Jian He commented on YARN-4519: --- committed in 2.8 too > potential deadlock of CapacityScheduler between

[jira] [Updated] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

[ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4519: -- Target Version/s: 2.8.0 (was: 2.9.0) > potential deadlock of CapacityScheduler between decrease container and

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

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

[jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers

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

[jira] [Commented] (YARN-3223) Resource update during NM graceful decommission

[ https://issues.apache.org/jira/browse/YARN-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142170#comment-15142170 ] Brook Zhou commented on YARN-3223: -- Hi [~djp], can you please review? > Resource update during NM

[jira] [Commented] (YARN-2575) Consider creating separate ACLs for Reservation create/update/delete/list ops

[ https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141920#comment-15141920 ] Sean Po commented on YARN-2575: --- Created a JIRA for documentation of Reservation ACLs. > Consider creating

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

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

[jira] [Commented] (YARN-2575) Consider creating separate ACLs for Reservation create/update/delete/list ops

[ https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141947#comment-15141947 ] Sean Po commented on YARN-2575: --- YARN-4687 > Consider creating separate ACLs for Reservation

[jira] [Updated] (YARN-2575) Consider creating separate ACLs for Reservation create/update/delete/list ops

[ https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-2575: - Description: YARN-1051 introduces the ReservationSystem and in the current implementation anyone

[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.003.patch > Automatic and Asynchronous Decommissioning Nodes Status Tracking >

[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: (was: graceful-decommission-v2.patch) > Automatic and Asynchronous Decommissioning Nodes

[jira] [Commented] (YARN-4420) Add REST API for List Reservations

[ https://issues.apache.org/jira/browse/YARN-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141908#comment-15141908 ] Subru Krishnan commented on YARN-4420: -- Thanks [~seanpo03] for contributing the patch and [~curino]

[jira] [Commented] (YARN-4468) Document the general ReservationSystem functionality, and the REST API

[ https://issues.apache.org/jira/browse/YARN-4468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15141909#comment-15141909 ] Carlo Curino commented on YARN-4468: [~subru] volunteered, to include in this patch the configuration

[jira] [Created] (YARN-4687) Document Reservation ACLs

Sean Po created YARN-4687: - Summary: Document Reservation ACLs Key: YARN-4687 URL: https://issues.apache.org/jira/browse/YARN-4687 Project: Hadoop YARN Issue Type: Task Reporter: Sean Po

[jira] [Updated] (YARN-2575) Consider creating separate ACLs for Reservation create/update/delete/list ops

[ https://issues.apache.org/jira/browse/YARN-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Po updated YARN-2575: -- Description: YARN-1051 introduces the ReservationSystem and in the current implementation anyone who can submit

[jira] [Updated] (YARN-4687) Document Reservation ACLs

[ https://issues.apache.org/jira/browse/YARN-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4687: - Issue Type: Sub-task (was: Task) Parent: YARN-2572 > Document Reservation ACLs >

[jira] [Commented] (YARN-2575) Consider creating separate ACLs for Reservation create/update/delete/list ops

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

[jira] [Updated] (YARN-4420) Add REST API for List Reservations

[ https://issues.apache.org/jira/browse/YARN-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4420: - Description: This JIRA tracks changes to the REST APIs of the reservation system and enables

[jira] [Updated] (YARN-4683) Document the List Reservations REST API

[ https://issues.apache.org/jira/browse/YARN-4683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4683: - Description: YARN-4420 adds a REST API to list existing reservations in the Plan. This JIRA