[jira] [Created] (YARN-2142) Add one service to check the nodes' TRUST status

anders created YARN-2142: Summary: Add one service to check the nodes' TRUST status Key: YARN-2142 URL: https://issues.apache.org/jira/browse/YARN-2142 Project: Hadoop YARN Issue Type: New Feature

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026159#comment-14026159 ] Vinod Kumar Vavilapalli commented on YARN-1408: --- Pitching in late, apologies.

[jira] [Commented] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026161#comment-14026161 ] Hadoop QA commented on YARN-2130: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1964) Create Docker analog of the LinuxContainerExecutor in YARN

[ https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026170#comment-14026170 ] Dinesh Subhraveti commented on YARN-1964: - We are putting together issues across

[jira] [Commented] (YARN-2124) ProportionalCapacityPreemptionPolicy cannot work because it's initialized before scheduler initialized

[ https://issues.apache.org/jira/browse/YARN-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026171#comment-14026171 ] Wangda Tan commented on YARN-2124: -- [~jianhe], Good catch, I'll try to see if RM.start can

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026187#comment-14026187 ] Sunil G commented on YARN-1408: --- Yes [~vinodkv]. +1 for the killContainer api in

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026192#comment-14026192 ] Vinod Kumar Vavilapalli commented on YARN-1408: --- bq. In this scenario, I hope

[jira] [Created] (YARN-2143) Merge common killContainer logic of Fair/Capacity scheduler into AbstractYarnScheduler

Wangda Tan created YARN-2143: Summary: Merge common killContainer logic of Fair/Capacity scheduler into AbstractYarnScheduler Key: YARN-2143 URL: https://issues.apache.org/jira/browse/YARN-2143 Project:

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026210#comment-14026210 ] Wangda Tan commented on YARN-1408: -- [~vinodkv], thanks for jumping in, +1 for put common

[jira] [Updated] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1365: Attachment: YARN-1365.004.patch 1) Added a flag to AppAttemptAddedSchedulerEvent that tells

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026243#comment-14026243 ] Sunil G commented on YARN-1408: --- Thank you Vinod. As discussed, I will work on a patch for

[jira] [Commented] (YARN-2030) Use StateMachine to simplify handleStoreEvent() in RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026336#comment-14026336 ] Hudson commented on YARN-2030: -- FAILURE: Integrated in Hadoop-Yarn-trunk #579 (See

[jira] [Updated] (YARN-2129) Add scheduling priority to the WindowsSecureContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2129: --- Attachment: YARN-2129.2.patch This patch moves the priority boost at the java.exe launch call, thus

[jira] [Commented] (YARN-1339) Recover DeletionService state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026413#comment-14026413 ] Junping Du commented on YARN-1339: -- Patch looks good overall. Some minor comments: In

[jira] [Commented] (YARN-2030) Use StateMachine to simplify handleStoreEvent() in RMStateStore

[ https://issues.apache.org/jira/browse/YARN-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026453#comment-14026453 ] Hudson commented on YARN-2030: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1770 (See

[jira] [Commented] (YARN-2130) Cleanup: Adding getRMAppManager, getQueueACLsManager, getApplicationACLsManager to RMContext

[ https://issues.apache.org/jira/browse/YARN-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026502#comment-14026502 ] Tsuyoshi OZAWA commented on YARN-2130: -- Updated a patch. It includes following

[jira] [Commented] (YARN-2124) ProportionalCapacityPreemptionPolicy cannot work because it's initialized before scheduler initialized

[ https://issues.apache.org/jira/browse/YARN-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026542#comment-14026542 ] Wangda Tan commented on YARN-2124: -- Hi [~jianhe], After thinking about this, I think we

[jira] [Updated] (YARN-1424) RMAppAttemptImpl should precompute a zeroed ApplicationResourceUsageReport to return when attempt not active

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-1424: - Attachment: YARN1424-04.patch Updated with Karthik's comments: - Fixed line length in

[jira] [Updated] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1514: - Attachment: YARN-1514.wip-2.patch Utility to benchmark ZKRMStateStore#loadState for

[jira] [Commented] (YARN-2140) Add support for network IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026672#comment-14026672 ] Bikas Saha commented on YARN-2140: -- [~ywskycn] For this and YARN-2139 my suggestion would

[jira] [Commented] (YARN-2140) Add support for network IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026674#comment-14026674 ] Wei Yan commented on YARN-2140: --- Thanks, [~bikassaha]. Yes, I'm working on that part. Add

[jira] [Commented] (YARN-2140) Add support for network IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026675#comment-14026675 ] Sandy Ryza commented on YARN-2140: -- +1 to a design sketch with alternatives Add support

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should precompute a zeroed ApplicationResourceUsageReport to return when attempt not active

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026688#comment-14026688 ] Hadoop QA commented on YARN-1424: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026741#comment-14026741 ] Tsuyoshi OZAWA commented on YARN-1514: -- Attached wip version 2 patch. 1. number of

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026789#comment-14026789 ] Mayank Bansal commented on YARN-2022: - Hi [~sunilg] Thanks for the update. We are in

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026795#comment-14026795 ] Mayank Bansal commented on YARN-2022: - for user limits there is already a jira

[jira] [Commented] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026839#comment-14026839 ] Ashwin Shankar commented on YARN-2134: -- Hi [~octo47], In your patch,there seems to be

[jira] [Commented] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings

[ https://issues.apache.org/jira/browse/YARN-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026849#comment-14026849 ] Andrey Stepachev commented on YARN-2134: This is a first of two patches for deep

[jira] [Commented] (YARN-1424) RMAppAttemptImpl should precompute a zeroed ApplicationResourceUsageReport to return when attempt not active

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026847#comment-14026847 ] Karthik Kambatla commented on YARN-1424: Latest patch looks good to me. +1.

[jira] [Updated] (YARN-1424) RMAppAttemptImpl should return the DummyApplicationResourceUsageReport for all invalid accesses

[ https://issues.apache.org/jira/browse/YARN-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1424: --- Summary: RMAppAttemptImpl should return the DummyApplicationResourceUsageReport for all

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026854#comment-14026854 ] Carlo Curino commented on YARN-2022: Mayank, I think it make sense keeping it simple

[jira] [Commented] (YARN-2141) Resource consumption logging

[ https://issues.apache.org/jira/browse/YARN-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026914#comment-14026914 ] Karthik Kambatla commented on YARN-2141: I have been meaning to take a stab at it

[jira] [Commented] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026917#comment-14026917 ] Karthik Kambatla commented on YARN-2083: Fix version is set at the time of commit

[jira] [Updated] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2083: --- Target Version/s: 2.5.0 (was: 2.3.0) In fair scheduler, Queue should not been assigned more

[jira] [Updated] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2083: --- Fix Version/s: (was: 2.3.0) In fair scheduler, Queue should not been assigned more

[jira] [Updated] (YARN-2091) Add more values to ContainerExitStatus and pass it from NM to RM and then to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-2091: - Summary: Add more values to ContainerExitStatus and pass it from NM to RM and then to app masters (was:

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026935#comment-14026935 ] Wei Yan commented on YARN-2139: --- For the disk IO, we can use cgroup to limit the IO usage for

[jira] [Commented] (YARN-2091) Add more values to ContainerExitStatus and pass it from NM to RM and then to app masters

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

[jira] [Commented] (YARN-2091) Add more values to ContainerExitStatus and pass it from NM to RM and then to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026968#comment-14026968 ] Tsuyoshi OZAWA commented on YARN-2091: -- Thanks Bikas and Vinod for reviews, and thanks

[jira] [Commented] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026967#comment-14026967 ] Wei Yan commented on YARN-2083: --- [~tianyi], here are some comments. 1. The tab size should be

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027012#comment-14027012 ] Jian He commented on YARN-1365: --- Anubhav, thanks for working on the patch. some comments:

[jira] [Updated] (YARN-1339) Recover DeletionService state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1339: - Attachment: YARN-1339v6.patch Thanks for the review, Junping! bq. Shall we add if

[jira] [Updated] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-2022: -- Attachment: YARN-2022.2.patch Thank you Mayank and Carlo. I have attached a patch as per discussion. Kindly

[jira] [Commented] (YARN-1339) Recover DeletionService state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027101#comment-14027101 ] Hadoop QA commented on YARN-1339: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027118#comment-14027118 ] Anubhav Dhoot commented on YARN-1365: - If an app did not register and do unregister

[jira] [Resolved] (YARN-1202) Verify RM HA works in secure clusters

[ https://issues.apache.org/jira/browse/YARN-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1202. --- Resolution: Won't Fix Assignee: (was: Wing Yew Poon)

[jira] [Created] (YARN-2144) Add logs when preemption occurs

Tassapol Athiapinya created YARN-2144: - Summary: Add logs when preemption occurs Key: YARN-2144 URL: https://issues.apache.org/jira/browse/YARN-2144 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027187#comment-14027187 ] Bikas Saha commented on YARN-1365: -- Sounds like the right approach. Keeps things

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027189#comment-14027189 ] Jian He commented on YARN-1365: --- Doing resync also for unregister is to keep the semantics

[jira] [Updated] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1514: - Attachment: YARN-1514.1.patch Utility to benchmark ZKRMStateStore#loadState for

[jira] [Commented] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027224#comment-14027224 ] Tsuyoshi OZAWA commented on YARN-1514: -- Updated a patch. This patch includes following

[jira] [Commented] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027255#comment-14027255 ] Hadoop QA commented on YARN-1514: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2124) ProportionalCapacityPreemptionPolicy cannot work because it's initialized before scheduler initialized

[ https://issues.apache.org/jira/browse/YARN-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027256#comment-14027256 ] Jian He commented on YARN-2124: --- I think we can move getRMActiveService from ResourceManager

[jira] [Commented] (YARN-2125) ProportionalCapacityPreemptionPolicy should only log CSV when debug enabled

[ https://issues.apache.org/jira/browse/YARN-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027263#comment-14027263 ] Jian He commented on YARN-2125: --- LOG.info(sb.toString()); inside should be changed as debug

[jira] [Updated] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1514: - Attachment: YARN-1514.2.patch Fixed javac warning by adding SuppressWarning annotation. Utility

[jira] [Updated] (YARN-2124) ProportionalCapacityPreemptionPolicy cannot work because it's initialized before scheduler initialized

[ https://issues.apache.org/jira/browse/YARN-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2124: - Attachment: YARN-2124.patch Uploaded patch addressed [~jianhe]'s suggestion, move getRMActiveService from

[jira] [Commented] (YARN-1621) Add CLI to list states of yarn container-IDs/hosts

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027284#comment-14027284 ] Tassapol Athiapinya commented on YARN-1621: --- yarnapplicationattempt lists only AM

[jira] [Updated] (YARN-2125) ProportionalCapacityPreemptionPolicy should only log CSV when debug enabled

[ https://issues.apache.org/jira/browse/YARN-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2125: - Attachment: YARN-2125.patch Uploaded a new patch addressed Jian's suggestion.

[jira] [Updated] (YARN-1621) Add CLI to list states of yarn container-IDs/hosts

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tassapol Athiapinya updated YARN-1621: -- Description: As more applications are moved to YARN, we need generic CLI to list rows

[jira] [Updated] (YARN-1621) Add CLI to list rows of task attempt ID, container ID, host of container, state of container

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tassapol Athiapinya updated YARN-1621: -- Summary: Add CLI to list rows of task attempt ID, container ID, host of container,

[jira] [Commented] (YARN-1621) Add CLI to list rows of task attempt ID, container ID, host of container, state of container

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027291#comment-14027291 ] Tassapol Athiapinya commented on YARN-1621: --- I updated jira info to not only list

[jira] [Updated] (YARN-2126) The FSLeafQueue.amResourceUsage shouldn't be updated when an Application removed before it runs AM

[ https://issues.apache.org/jira/browse/YARN-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2126: -- Assignee: (was: Wei Yan) The FSLeafQueue.amResourceUsage shouldn't be updated when an Application

[jira] [Commented] (YARN-1514) Utility to benchmark ZKRMStateStore#loadState for ResourceManager-HA

[ https://issues.apache.org/jira/browse/YARN-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027317#comment-14027317 ] Hadoop QA commented on YARN-1514: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2125) ProportionalCapacityPreemptionPolicy should only log CSV when debug enabled

[ https://issues.apache.org/jira/browse/YARN-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027328#comment-14027328 ] Hadoop QA commented on YARN-2125: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2140) Add support for network IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027332#comment-14027332 ] haosdent commented on YARN-2140: Cool ! Add support for network IO isolation/scheduling

[jira] [Commented] (YARN-2124) ProportionalCapacityPreemptionPolicy cannot work because it's initialized before scheduler initialized

[ https://issues.apache.org/jira/browse/YARN-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027333#comment-14027333 ] Hadoop QA commented on YARN-2124: - {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027357#comment-14027357 ] Steve Loughran commented on YARN-2139: -- I don't think I was clear enough, sorry HDFS

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027359#comment-14027359 ] Sandy Ryza commented on YARN-2139: -- With short-circuit local reads, reads on local data do

[jira] [Commented] (YARN-2141) Resource consumption logging

[ https://issues.apache.org/jira/browse/YARN-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027366#comment-14027366 ] Carlo Curino commented on YARN-2141: This is great.. feel free to reach out to me if

[jira] [Commented] (YARN-2139) Add support for disk IO isolation/scheduling for containers

[ https://issues.apache.org/jira/browse/YARN-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027379#comment-14027379 ] Alejandro Abdelnur commented on YARN-2139: -- As Sandy says, for local reads short

[jira] [Updated] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Tian updated YARN-2083: -- Fix Version/s: 2.5.0 In fair scheduler, Queue should not been assigned more containers when its usedResource

[jira] [Updated] (YARN-1621) Add CLI to list rows of task attempt ID, container ID, host of container, state of container

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tassapol Athiapinya updated YARN-1621: -- Description: As more applications are moved to YARN, we need generic CLI to list rows

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14027431#comment-14027431 ] Hadoop QA commented on YARN-2022: - {color:red}-1 overall{color}. Here are the results of