[jira] [Commented] (YARN-2080) Admission Control: Integrate Reservation subsystem with ResourceManager

[ https://issues.apache.org/jira/browse/YARN-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044394#comment-14044394 ] Karthik Kambatla commented on YARN-2080: Thanks for the patch, Subru. Just skimmed

[jira] [Commented] (YARN-1710) Admission Control: agents to allocate reservation

[ https://issues.apache.org/jira/browse/YARN-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044414#comment-14044414 ] Carlo Curino commented on YARN-1710: As discussed before the patches are not meant to

[jira] [Updated] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

[ https://issues.apache.org/jira/browse/YARN-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1713: Attachment: apache-yarn-1713.7.patch bq.RMWebServices.submitNewApplication submitApplication

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

[ https://issues.apache.org/jira/browse/YARN-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] anders updated YARN-2142: - Attachment: (was: test.patch) Add one service to check the nodes' TRUST status

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

[ https://issues.apache.org/jira/browse/YARN-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lijuan Zhang updated YARN-2142: --- Attachment: trust.patch Add one service to check the nodes' TRUST status

[jira] [Updated] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2181: - Attachment: YARN-2181.patch Updated patch, make methods/fields name more consistent. Add preemption

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

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

[jira] [Commented] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

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

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

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

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

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

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

[ https://issues.apache.org/jira/browse/YARN-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] anders updated YARN-2142: - Attachment: test.patch test Add one service to check the nodes' TRUST status

[jira] [Assigned] (YARN-2004) Priority scheduling support in Capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G reassigned YARN-2004: - Assignee: Sunil G Priority scheduling support in Capacity scheduler

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

[ https://issues.apache.org/jira/browse/YARN-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044532#comment-14044532 ] Hadoop QA commented on YARN-2142: - {color:red}-1 overall{color}. Here are the results 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=14044535#comment-14044535 ] Sunil G commented on YARN-2022: --- Hi [~mayank_bansal] and [~leftnoteasy] I was checking few

[jira] [Updated] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

[ https://issues.apache.org/jira/browse/YARN-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1713: Attachment: apache-yarn-1713.8.patch Fixed javadoc warnings. Implement getnewapplication and

[jira] [Updated] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2181: - Attachment: YARN-2181.patch Addressed UT failures and findbugs. I noticed TestRMApplicationHistoryWriter

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044547#comment-14044547 ] Wangda Tan commented on YARN-2181: -- Created YARN-2215 to track effort of adding preemption

[jira] [Created] (YARN-2215) Add preemption info to REST/CLI

Wangda Tan created YARN-2215: Summary: Add preemption info to REST/CLI Key: YARN-2215 URL: https://issues.apache.org/jira/browse/YARN-2215 Project: Hadoop YARN Issue Type: Bug

[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=14044548#comment-14044548 ] Wangda Tan commented on YARN-1408: -- Hi [~sunilg], do you have any updates on this issue,

[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=14044553#comment-14044553 ] Sunil G commented on YARN-1408: --- Hi [~leftnoteasy] As discussed in YARN-2143 last day, I am

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

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

[jira] [Updated] (YARN-2201) TestRMWebServicesAppsModification dependent on yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2201: Attachment: apache-yarn-2201.2.patch Uploaded new patch which should take care both issues.

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

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

[jira] [Commented] (YARN-2171) AMs block on the CapacityScheduler lock during allocate()

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

[jira] [Commented] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

[ https://issues.apache.org/jira/browse/YARN-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044576#comment-14044576 ] Varun Vasudev commented on YARN-1713: - Test failure is unrelated. Implement

[jira] [Commented] (YARN-2201) TestRMWebServicesAppsModification dependent on yarn-default.xml

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

[jira] [Commented] (YARN-2201) TestRMWebServicesAppsModification dependent on yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044598#comment-14044598 ] Varun Vasudev commented on YARN-2201: - Test failure is unrelated to the patch.

[jira] [Created] (YARN-2216) TestRMApplicationHistoryWriter sometimes fails in trunk

Ted Yu created YARN-2216: Summary: TestRMApplicationHistoryWriter sometimes fails in trunk Key: YARN-2216 URL: https://issues.apache.org/jira/browse/YARN-2216 Project: Hadoop YARN Issue Type: Test

Anyone know how to mock a secured hdfs for unit test?

Hi all, I need to test my code which read data from secured hdfs, is there any library to mock secured hdfs, can minihdfscluster do the work? Any suggestion is appreciated. Thanks

[jira] [Assigned] (YARN-2216) TestRMApplicationHistoryWriter sometimes fails in trunk

[ https://issues.apache.org/jira/browse/YARN-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen reassigned YARN-2216: - Assignee: Zhijie Shen TestRMApplicationHistoryWriter sometimes fails in trunk

[jira] [Commented] (YARN-2216) TestRMApplicationHistoryWriter sometimes fails in trunk

[ https://issues.apache.org/jira/browse/YARN-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044690#comment-14044690 ] Zhijie Shen commented on YARN-2216: --- The reason should be the same as we found in

RE: Anyone know how to mock a secured hdfs for unit test?

Hi David, Quite some time ago I opened HADOOP-9952 and planned to create secured MiniClusters by making use of MiniKDC. Unfortunately since then I didn't get the chance to work on it yet. If you need something like that and would contribute, please let me know and see if anything I can help

[jira] [Updated] (YARN-2216) TestRMApplicationHistoryWriter sometimes fails in trunk

[ https://issues.apache.org/jira/browse/YARN-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2216: -- Attachment: YARN-2216.1.patch Use the strategy in YARN-1907 to fix the problem

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

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

[jira] [Commented] (YARN-2171) AMs block on the CapacityScheduler lock during allocate()

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

[jira] [Commented] (YARN-1810) YARN RM Webapp Application page Issue

[ https://issues.apache.org/jira/browse/YARN-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044737#comment-14044737 ] Peng Zhang commented on YARN-1810: -- I found if click default queue bar, all running

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

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

[jira] [Commented] (YARN-2171) AMs block on the CapacityScheduler lock during allocate()

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

[jira] [Commented] (YARN-2216) TestRMApplicationHistoryWriter sometimes fails in trunk

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

[jira] [Commented] (YARN-2216) TestRMApplicationHistoryWriter sometimes fails in trunk

[ https://issues.apache.org/jira/browse/YARN-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044803#comment-14044803 ] Ted Yu commented on YARN-2216: -- lgtm TestRMApplicationHistoryWriter sometimes fails in trunk

[jira] [Commented] (YARN-2201) TestRMWebServicesAppsModification dependent on yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044839#comment-14044839 ] Ray Chiang commented on YARN-2201: -- Okay, I've run the test locally and made sure that it

[jira] [Updated] (YARN-2216) TestRMApplicationHistoryWriter sometimes fails in trunk

[ https://issues.apache.org/jira/browse/YARN-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated YARN-2216: - Attachment: TestRMApplicationHistoryWriter.stack Stack trace for TestRMApplicationHistoryWriter which took long

[jira] [Updated] (YARN-2214) preemptContainerPreCheck() in FSParentQueue delays convergence towards fairness

[ https://issues.apache.org/jira/browse/YARN-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Shankar updated YARN-2214: - Attachment: YARN-2214-v1.txt Attached patch removes preemptContainerPreCheck from

[jira] [Commented] (YARN-2216) TestRMApplicationHistoryWriter sometimes fails in trunk

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

[jira] [Commented] (YARN-2214) preemptContainerPreCheck() in FSParentQueue delays convergence towards fairness

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

[jira] [Commented] (YARN-2214) preemptContainerPreCheck() in FSParentQueue delays convergence towards fairness

[ https://issues.apache.org/jira/browse/YARN-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14044964#comment-14044964 ] Ashwin Shankar commented on YARN-2214: -- test failure not related to this patch. There

[jira] [Updated] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-614: --- Attachment: YARN-614.8.patch Separate AM failures from hardware failure or YARN error and do not count them

[jira] [Commented] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

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

[jira] [Commented] (YARN-941) RM Should have a way to update the tokens it has for a running application

[ https://issues.apache.org/jira/browse/YARN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045062#comment-14045062 ] bc Wong commented on YARN-941: -- Hi [~vinodkv], could you elaborate more on the point about

[jira] [Commented] (YARN-2194) Add Cgroup support for RedHat 7

[ https://issues.apache.org/jira/browse/YARN-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045097#comment-14045097 ] Alejandro Abdelnur commented on YARN-2194: -- do we need to have a special container

[jira] [Commented] (YARN-2194) Add Cgroup support for RedHat 7

[ https://issues.apache.org/jira/browse/YARN-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045101#comment-14045101 ] Wei Yan commented on YARN-2194: --- [~tucu00], you mean just detect whether the system is RedHat

[jira] [Commented] (YARN-2194) Add Cgroup support for RedHat 7

[ https://issues.apache.org/jira/browse/YARN-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045105#comment-14045105 ] Alejandro Abdelnur commented on YARN-2194: -- i was not meaning autodetection, i was

[jira] [Commented] (YARN-2194) Add Cgroup support for RedHat 7

[ https://issues.apache.org/jira/browse/YARN-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045110#comment-14045110 ] Wei Yan commented on YARN-2194: --- oh, yes, adding a new LCEResourceHandler to handle the

[jira] [Commented] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045121#comment-14045121 ] Jian He commented on YARN-614: -- - shouldNotCountFailureToAttemptLimit, how about

[jira] [Updated] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-2204: Attachment: YARN-2204_addendum.patch I re-looked at this and saw that I could do this much simpler

[jira] [Updated] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2052: - Attachment: YARN-2052.7.patch ContainerId creation after work preserving restart is broken

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045164#comment-14045164 ] Tsuyoshi OZAWA commented on YARN-2052: -- Thank you for the review, Jian! Updated a

[jira] [Updated] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Shankar updated YARN-2026: - Attachment: YARN-2026-v2.txt Attached patch implements two new scheduling policies -

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045221#comment-14045221 ] Jian He commented on YARN-2181: --- - getNumNonAMContainersPreempted calls

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

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

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

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

[jira] [Commented] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045259#comment-14045259 ] Xuan Gong commented on YARN-614: bq. shouldNotCountFailureToAttemptLimit, how about

[jira] [Updated] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-614: --- Attachment: YARN-614.9.patch Separate AM failures from hardware failure or YARN error and do not count them

[jira] [Created] (YARN-2217) Shared cache client side changes

Chris Trezzo created YARN-2217: -- Summary: Shared cache client side changes Key: YARN-2217 URL: https://issues.apache.org/jira/browse/YARN-2217 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045265#comment-14045265 ] Jian He commented on YARN-2052: --- hmm, we need to think about toString compatibility too,

[jira] [Updated] (YARN-2217) Shared cache client side changes

[ https://issues.apache.org/jira/browse/YARN-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated YARN-2217: --- Attachment: YARN-2217-trunk-v1.patch Attached is a v1 patch on

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

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

[jira] [Commented] (YARN-1367) After restart NM should resync with the RM without killing containers

[ https://issues.apache.org/jira/browse/YARN-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045293#comment-14045293 ] Vinod Kumar Vavilapalli commented on YARN-1367: --- Sorry for jumping in late,

[jira] [Updated] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2052: - Attachment: YARN-2052.8.patch Yeah, I agree with leaving {{ContainerId#toString}} related problem

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045298#comment-14045298 ] Vinod Kumar Vavilapalli commented on YARN-2052: --- I cursorily looked. Some

[jira] [Commented] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

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

[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=14045303#comment-14045303 ] Wangda Tan commented on YARN-1408: -- Thanks [~sunilg], looking forward your patch :)

[jira] [Commented] (YARN-1810) YARN RM Webapp Application page Issue

[ https://issues.apache.org/jira/browse/YARN-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045310#comment-14045310 ] Wangda Tan commented on YARN-1810: -- This should be caused by

[jira] [Commented] (YARN-1367) After restart NM should resync with the RM without killing containers

[ https://issues.apache.org/jira/browse/YARN-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045311#comment-14045311 ] Jian He commented on YARN-1367: --- agree, given the flag will be got rid of in the future, it's

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045313#comment-14045313 ] Tsuyoshi OZAWA commented on YARN-2052: -- Thank you for suggestions, Vinod! I'll update

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045320#comment-14045320 ] Karthik Kambatla commented on YARN-2204: Addendum looks good. +1

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045323#comment-14045323 ] Karthik Kambatla commented on YARN-2204: Thanks Jian and Vinod for your reviews. If

[jira] [Commented] (YARN-2200) Rename related container start time to container creation time

[ https://issues.apache.org/jira/browse/YARN-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045324#comment-14045324 ] Karthik Kambatla commented on YARN-2200: Is the plan to add a separate start time?

[jira] [Updated] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-614: --- Attachment: YARN-614.10.patch fix some comment changes, and merge the testcases Separate AM failures from

[jira] [Commented] (YARN-2204) TestAMRestart#testAMRestartWithExistingContainers assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-2204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045325#comment-14045325 ] Jian He commented on YARN-2204: --- lgtm TestAMRestart#testAMRestartWithExistingContainers

[jira] [Updated] (YARN-2195) Clean a piece of code in ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2195: --- Priority: Trivial (was: Minor) Clean a piece of code in ResourceRequest

[jira] [Commented] (YARN-2200) Rename related container start time to container creation time

[ https://issues.apache.org/jira/browse/YARN-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045343#comment-14045343 ] Jian He commented on YARN-2200: --- This jira is only to rename the corresponding start time to

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

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

[jira] [Commented] (YARN-2200) Rename related container start time to container creation time

[ https://issues.apache.org/jira/browse/YARN-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045350#comment-14045350 ] Jian He commented on YARN-2200: --- I think it's better to rename this now than future, even if

[jira] [Updated] (YARN-2181) Add preemption info to RM Web UI

[ https://issues.apache.org/jira/browse/YARN-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2181: - Attachment: YARN-2181.patch Thanks for your comments, Address all comments and uploaded a new patch.

[jira] [Updated] (YARN-2113) CS queue level preemption should respect user-limits

[ https://issues.apache.org/jira/browse/YARN-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2113: -- Summary: CS queue level preemption should respect user-limits (was: CS

[jira] [Updated] (YARN-2080) Admission Control: Integrate Reservation subsystem with ResourceManager

[ https://issues.apache.org/jira/browse/YARN-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subramaniam Venkatraman Krishnan updated YARN-2080: --- Attachment: YARN-2080.patch Thanks for the feedback [~kasha].

[jira] [Updated] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2052: - Attachment: YARN-2052.9.patch ContainerId creation after work preserving restart is broken

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

[ https://issues.apache.org/jira/browse/YARN-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045373#comment-14045373 ] Tsuyoshi OZAWA commented on YARN-2052: -- * Renamed RMEpochProto to EpochProto. * Bump

[jira] [Commented] (YARN-2080) Admission Control: Integrate Reservation subsystem with ResourceManager

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

[jira] [Commented] (YARN-614) Separate AM failures from hardware failure or YARN error and do not count them to AM retry count

[ https://issues.apache.org/jira/browse/YARN-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045385#comment-14045385 ] Hadoop QA commented on YARN-614: {color:red}-1 overall{color}. Here are the results 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=14045386#comment-14045386 ] Mayank Bansal commented on YARN-2022: - You are using getAbsoluteMaximumCapacity() in

[jira] [Created] (YARN-2218) TestSubmitApplicationWithRMHA fails intermittently in trunk

Ashwin Shankar created YARN-2218: Summary: TestSubmitApplicationWithRMHA fails intermittently in trunk Key: YARN-2218 URL: https://issues.apache.org/jira/browse/YARN-2218 Project: Hadoop YARN

[jira] [Created] (YARN-2219) TestWorkPreservingRMRestart fails intermittently on trunk

Ashwin Shankar created YARN-2219: Summary: TestWorkPreservingRMRestart fails intermittently on trunk Key: YARN-2219 URL: https://issues.apache.org/jira/browse/YARN-2219 Project: Hadoop YARN

[jira] [Created] (YARN-2220) TestAMRestart#testAMPreemptedNotCountedForAMFailures times out on trunk intermittently

Ashwin Shankar created YARN-2220: Summary: TestAMRestart#testAMPreemptedNotCountedForAMFailures times out on trunk intermittently Key: YARN-2220 URL: https://issues.apache.org/jira/browse/YARN-2220

[jira] [Commented] (YARN-2181) Add preemption info to RM Web UI

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

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14045401#comment-14045401 ] Ashwin Shankar commented on YARN-2026: -- Test failures are unrelated to the patch.First

[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.8.patch Thank you [~mayank_bansal] for the review. I have updated the patch by changing

[jira] [Commented] (YARN-2052) ContainerId creation after work preserving restart is broken

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

[jira] [Updated] (YARN-415) Capture memory utilization at the app-level for chargeback

[ https://issues.apache.org/jira/browse/YARN-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-415: Attachment: YARN-415.201406262136.txt Upmerging again so patch will cleanly apply to both trunk and branch-2

  1   2   >