[jira] [Updated] (YARN-2283) RM failed to release the AM container

[ https://issues.apache.org/jira/browse/YARN-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishan Shetty updated YARN-2283: Affects Version/s: (was: 2.5.0) 2.4.0 RM failed to release the AM

[jira] [Commented] (YARN-2427) Add support for moving apps between queues in RM web services

[ https://issues.apache.org/jira/browse/YARN-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108787#comment-14108787 ] Tsuyoshi OZAWA commented on YARN-2427: -- Hi [~vvasudev], how about calling rm.stop in

[jira] [Updated] (YARN-2427) Add support for moving apps between queues in RM web services

[ https://issues.apache.org/jira/browse/YARN-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2427: Attachment: apache-yarn-2427.1.patch [~ozawa] thanks for the suggestion! I thought the tearDown

[jira] [Updated] (YARN-2448) RM should expose the name of the ResourceCalculator being used when AMs register

[ https://issues.apache.org/jira/browse/YARN-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2448: Attachment: apache-yarn-2448.1.patch I didn't do a clean which led to me missing an override in

[jira] [Resolved] (YARN-2435) Capacity scheduler should only allow Kill Application Requests from ADMINISTER_QUEUE users

[ https://issues.apache.org/jira/browse/YARN-2435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amir Mal resolved YARN-2435. Resolution: Invalid I was missing the following setting in my yarn-site.xml: yarn.acl.enable = true

[jira] [Commented] (YARN-2448) RM should expose the name of the ResourceCalculator being used when AMs register

[ https://issues.apache.org/jira/browse/YARN-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108822#comment-14108822 ] Wangda Tan commented on YARN-2448: -- [~vvasudev], Thanks for working on the patch, it is

[jira] [Commented] (YARN-2427) Add support for moving apps between queues in RM web services

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

[jira] [Commented] (YARN-2448) RM should expose the name of the ResourceCalculator being used when AMs register

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

[jira] [Updated] (YARN-2427) Add support for moving apps between queues in RM web services

[ https://issues.apache.org/jira/browse/YARN-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2427: Attachment: apache-yarn-2427.2.patch That fixed some of the tests. I found a similar missing

[jira] [Created] (YARN-2449) Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when hadoop.http.filter.initializers are not set

Karam Singh created YARN-2449: - Summary: Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when hadoop.http.filter.initializers are not set Key: YARN-2449 URL:

[jira] [Updated] (YARN-2449) Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when hadoop.http.filter.initializers are not set

[ https://issues.apache.org/jira/browse/YARN-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karam Singh updated YARN-2449: -- Priority: Critical (was: Major) Timelineserver returns invalid Delegation token in secure kerberos

[jira] [Updated] (YARN-2449) Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when hadoop.http.filter.initializers are not set

[ https://issues.apache.org/jira/browse/YARN-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karam Singh updated YARN-2449: -- Description: Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when

[jira] [Commented] (YARN-2449) Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when hadoop.http.filter.initializers are not set

[ https://issues.apache.org/jira/browse/YARN-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108873#comment-14108873 ] Karam Singh commented on YARN-2449: --- Similarly If you run hadoop applications e.g.

[jira] [Updated] (YARN-2449) Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when hadoop.http.filter.initializers are not set

[ https://issues.apache.org/jira/browse/YARN-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karam Singh updated YARN-2449: -- Description: Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when

[jira] [Assigned] (YARN-2449) Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when hadoop.http.filter.initializers are not set

[ https://issues.apache.org/jira/browse/YARN-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reassigned YARN-2449: --- Assignee: Varun Vasudev Timelineserver returns invalid Delegation token in secure kerberos

[jira] [Commented] (YARN-2427) Add support for moving apps between queues in RM web services

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

[jira] [Commented] (YARN-1707) Making the CapacityScheduler more dynamic

[ https://issues.apache.org/jira/browse/YARN-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108932#comment-14108932 ] Wangda Tan commented on YARN-1707: -- Hi [~curino], Thanks for updating, I just took a look,

[jira] [Commented] (YARN-1707) Making the CapacityScheduler more dynamic

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

[jira] [Commented] (YARN-2427) Add support for moving apps between queues in RM web services

[ https://issues.apache.org/jira/browse/YARN-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108975#comment-14108975 ] Varun Vasudev commented on YARN-2427: - The TestAMRestart failure is unrelated. Add

[jira] [Updated] (YARN-2449) Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when hadoop.http.filter.initializers are not set

[ https://issues.apache.org/jira/browse/YARN-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2449: Attachment: apache-yarn-2449.0.patch Uploaded patch with fix. Timelineserver returns invalid

[jira] [Commented] (YARN-1198) Capacity Scheduler headroom calculation does not work as expected

[ https://issues.apache.org/jira/browse/YARN-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14108991#comment-14108991 ] Wangda Tan commented on YARN-1198: -- Hi [~cwelch], Thanks for updating, I went through your

[jira] [Commented] (YARN-2449) Timelineserver returns invalid Delegation token in secure kerberos enabled cluster when hadoop.http.filter.initializers are not set

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

[jira] [Updated] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

[ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-160: --- Attachment: apache-yarn-160.2.patch Comments from [~jlowe] in YARN-2440 about this feature led to some

[jira] [Commented] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

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

[jira] [Commented] (YARN-2035) FileSystemApplicationHistoryStore blocks RM and AHS while NN is in safemode

[ https://issues.apache.org/jira/browse/YARN-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109340#comment-14109340 ] Zhijie Shen commented on YARN-2035: --- +1 for the latest patch. Will commit it.

[jira] [Assigned] (YARN-2450) Fix typos in log messages

[ https://issues.apache.org/jira/browse/YARN-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang reassigned YARN-2450: Assignee: Ray Chiang Fix typos in log messages - Key:

[jira] [Created] (YARN-2450) Fix typos in log messages

Ray Chiang created YARN-2450: Summary: Fix typos in log messages Key: YARN-2450 URL: https://issues.apache.org/jira/browse/YARN-2450 Project: Hadoop YARN Issue Type: Bug Affects Versions:

[jira] [Updated] (YARN-2450) Fix typos in log messages

[ https://issues.apache.org/jira/browse/YARN-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-2450: - Attachment: YARN-2450-01.patch First attempt for YARN-only log fixes. Fix typos in log messages

[jira] [Comment Edited] (YARN-2035) FileSystemApplicationHistoryStore blocks RM and AHS while NN is in safemode

[ https://issues.apache.org/jira/browse/YARN-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109340#comment-14109340 ] Zhijie Shen edited comment on YARN-2035 at 8/25/14 6:01 PM: +1

[jira] [Commented] (YARN-810) Support CGroup ceiling enforcement on CPU

[ https://issues.apache.org/jira/browse/YARN-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109442#comment-14109442 ] Wei Yan commented on YARN-810: -- [~vvasudev], for the cfs_quota_us and cfs_period_us settings

[jira] [Commented] (YARN-2377) Localization exception stack traces are not passed as diagnostic info

[ https://issues.apache.org/jira/browse/YARN-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109479#comment-14109479 ] Karthik Kambatla commented on YARN-2377: +1 to improving the debuggability here.

[jira] [Commented] (YARN-2450) Fix typos in log messages

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

[jira] [Commented] (YARN-1326) RM should log using RMStore at startup time

[ https://issues.apache.org/jira/browse/YARN-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109490#comment-14109490 ] Karthik Kambatla commented on YARN-1326: Minor nit that I can fix at commit time:

[jira] [Commented] (YARN-2450) Fix typos in log messages

[ https://issues.apache.org/jira/browse/YARN-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109504#comment-14109504 ] Ray Chiang commented on YARN-2450: -- Changes restricted to log messages only. Will not

[jira] [Created] (YARN-2451) Delete .orig files

Karthik Kambatla created YARN-2451: -- Summary: Delete .orig files Key: YARN-2451 URL: https://issues.apache.org/jira/browse/YARN-2451 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-2450) Fix typos in log messages

[ https://issues.apache.org/jira/browse/YARN-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109524#comment-14109524 ] Akira AJISAKA commented on YARN-2450: - Thanks [~rchiang] for splitting the patch. LGTM,

[jira] [Commented] (YARN-2448) RM should expose the name of the ResourceCalculator being used when AMs register

[ https://issues.apache.org/jira/browse/YARN-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109577#comment-14109577 ] Karthik Kambatla commented on YARN-2448: I am not sure I understand the usecase

[jira] [Commented] (YARN-2448) RM should expose the name of the ResourceCalculator being used when AMs register

[ https://issues.apache.org/jira/browse/YARN-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109589#comment-14109589 ] Varun Vasudev commented on YARN-2448: - The use case that springs to mind is adding

[jira] [Commented] (YARN-2448) RM should expose the name of the ResourceCalculator being used when AMs register

[ https://issues.apache.org/jira/browse/YARN-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109603#comment-14109603 ] Karthik Kambatla commented on YARN-2448: May be I am missing your point. Why not

[jira] [Commented] (YARN-1198) Capacity Scheduler headroom calculation does not work as expected

[ https://issues.apache.org/jira/browse/YARN-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109738#comment-14109738 ] Craig Welch commented on YARN-1198: --- I initially considered an approach like this one,

[jira] [Commented] (YARN-1857) CapacityScheduler headroom doesn't account for other AM's running

[ https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109798#comment-14109798 ] Craig Welch commented on YARN-1857: --- [~jianhe] [~wangda] could you have a look at this

[jira] [Commented] (YARN-2440) Cgroups should allow YARN containers to be limited to allocated cores

[ https://issues.apache.org/jira/browse/YARN-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109801#comment-14109801 ] Jason Lowe commented on YARN-2440: -- Thanks for updating the patch, Varun. I don't see why

[jira] [Updated] (YARN-1857) CapacityScheduler headroom doesn't account for other AM's running

[ https://issues.apache.org/jira/browse/YARN-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-1857: -- Target Version/s: 2.6.0 (was: 2.4.1) CapacityScheduler headroom doesn't account for other AM's running

[jira] [Commented] (YARN-1442) change yarn minicluster base directory via system property

[ https://issues.apache.org/jira/browse/YARN-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109849#comment-14109849 ] Ken Krugler commented on YARN-1442: --- I'm curious why we wouldn't use the existing

[jira] [Commented] (YARN-2440) Cgroups should allow YARN containers to be limited to allocated cores

[ https://issues.apache.org/jira/browse/YARN-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109856#comment-14109856 ] Sangjin Lee commented on YARN-2440: --- It might be good to use several fairly

[jira] [Commented] (YARN-2182) Update ContainerId#toString() to avoid conflicts before and after RM restart

[ https://issues.apache.org/jira/browse/YARN-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14109943#comment-14109943 ] Jian He commented on YARN-2182: --- looks good, +1 Update ContainerId#toString() to avoid

[jira] [Commented] (YARN-2395) FairScheduler: Preemption timeout should be configurable per queue

[ https://issues.apache.org/jira/browse/YARN-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110007#comment-14110007 ] Karthik Kambatla commented on YARN-2395: Comments on the latest patch: # Typo -

[jira] [Updated] (YARN-2395) FairScheduler: Preemption timeout should be configurable per queue

[ https://issues.apache.org/jira/browse/YARN-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2395: -- Attachment: YARN-2395-3.patch Update a new patch to address Karthik's comments. FairScheduler: Preemption

[jira] [Commented] (YARN-2395) FairScheduler: Preemption timeout should be configurable per queue

[ https://issues.apache.org/jira/browse/YARN-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110059#comment-14110059 ] Ashwin Shankar commented on YARN-2395: -- [~ywskycn], I'll post my comments soon. But

[jira] [Created] (YARN-2452) TestRMApplicationHistoryWriter is failed for FairScheduler

zhihai xu created YARN-2452: --- Summary: TestRMApplicationHistoryWriter is failed for FairScheduler Key: YARN-2452 URL: https://issues.apache.org/jira/browse/YARN-2452 Project: Hadoop YARN Issue

[jira] [Created] (YARN-2453) TestProportionalCapacityPreemptionPolicy is failed for FairScheduler

zhihai xu created YARN-2453: --- Summary: TestProportionalCapacityPreemptionPolicy is failed for FairScheduler Key: YARN-2453 URL: https://issues.apache.org/jira/browse/YARN-2453 Project: Hadoop YARN

[jira] [Updated] (YARN-1198) Capacity Scheduler headroom calculation does not work as expected

[ https://issues.apache.org/jira/browse/YARN-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-1198: -- Attachment: YARN-1198.8.patch Patch based on my last comment which iterates/calculates headroom at the

[jira] [Updated] (YARN-2404) Remove ApplicationAttemptState and ApplicationState class in RMStateStore class

[ https://issues.apache.org/jira/browse/YARN-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-2404: -- Issue Type: Sub-task (was: Improvement) Parent: YARN-128 Remove ApplicationAttemptState and

[jira] [Commented] (YARN-2395) FairScheduler: Preemption timeout should be configurable per queue

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

[jira] [Commented] (YARN-2056) Disable preemption at Queue level

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

[jira] [Commented] (YARN-2377) Localization exception stack traces are not passed as diagnostic info

[ https://issues.apache.org/jira/browse/YARN-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110221#comment-14110221 ] Gera Shegalov commented on YARN-2377: - Hi [~kasha], I considered

[jira] [Commented] (YARN-2440) Cgroups should allow YARN containers to be limited to allocated cores

[ https://issues.apache.org/jira/browse/YARN-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110227#comment-14110227 ] Beckham007 commented on YARN-2440: -- Hi, all Why not use the cpuset subsystem of cgroups?

[jira] [Updated] (YARN-2406) Move RM recovery related proto to yarn_server_resourcemanager_recovery.proto

[ https://issues.apache.org/jira/browse/YARN-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2406: - Attachment: YARN-2406.1.patch Move RM recovery related proto to

[jira] [Commented] (YARN-1198) Capacity Scheduler headroom calculation does not work as expected

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

[jira] [Assigned] (YARN-2404) Remove ApplicationAttemptState and ApplicationState class in RMStateStore class

[ https://issues.apache.org/jira/browse/YARN-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA reassigned YARN-2404: Assignee: Tsuyoshi OZAWA Remove ApplicationAttemptState and ApplicationState class in

[jira] [Updated] (YARN-2453) TestProportionalCapacityPreemptionPolicy is failed for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2453: Attachment: YARN-2453.000.patch TestProportionalCapacityPreemptionPolicy is failed for FairScheduler

[jira] [Commented] (YARN-2406) Move RM recovery related proto to yarn_server_resourcemanager_recovery.proto

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

[jira] [Updated] (YARN-2452) TestRMApplicationHistoryWriter is failed for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-2452: Attachment: YARN-2452.000.patch TestRMApplicationHistoryWriter is failed for FairScheduler

[jira] [Commented] (YARN-2406) Move RM recovery related proto to yarn_server_resourcemanager_recovery.proto

[ https://issues.apache.org/jira/browse/YARN-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110269#comment-14110269 ] Tsuyoshi OZAWA commented on YARN-2406: -- The test failure looks not related to a patch.

[jira] [Commented] (YARN-2453) TestProportionalCapacityPreemptionPolicy is failed for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110272#comment-14110272 ] zhihai xu commented on YARN-2453: - I uploaded a patch YARN-2453.000.patch for review. This

[jira] [Commented] (YARN-2452) TestRMApplicationHistoryWriter is failed for FairScheduler

[ https://issues.apache.org/jira/browse/YARN-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110276#comment-14110276 ] zhihai xu commented on YARN-2452: - I uploaded a patch YARN-2452.000.patch for review. This

[jira] [Commented] (YARN-2453) TestProportionalCapacityPreemptionPolicy is failed for FairScheduler

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

[jira] [Commented] (YARN-2448) RM should expose the name of the ResourceCalculator being used when AMs register

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

[jira] [Commented] (YARN-2452) TestRMApplicationHistoryWriter is failed for FairScheduler

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