[jira] [Updated] (YARN-2394) FairScheduler: Configure fairSharePreemptionThreshold per queue

[ https://issues.apache.org/jira/browse/YARN-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2394: -- Attachment: YARN-2394-5.patch Update a patch addressing the latest comments. FairScheduler: Configure

[jira] [Reopened] (YARN-2158) TestRMWebServicesAppsModification sometimes fails in trunk

[ https://issues.apache.org/jira/browse/YARN-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reopened YARN-2158: - The test failed in trunk again. TestRMWebServicesAppsModification sometimes fails in trunk

[jira] [Updated] (YARN-2158) TestRMWebServicesAppsModification sometimes fails in trunk

[ https://issues.apache.org/jira/browse/YARN-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-2158: Attachment: apache-yarn-2158.1.patch Attaching patch with fix. TestRMWebServicesAppsModification

[jira] [Commented] (YARN-2394) FairScheduler: Configure fairSharePreemptionThreshold per queue

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

[jira] [Commented] (YARN-2158) TestRMWebServicesAppsModification sometimes fails in trunk

[ https://issues.apache.org/jira/browse/YARN-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118027#comment-14118027 ] Varun Vasudev commented on YARN-2158: - Forgot to mention, the patch also has some

[jira] [Commented] (YARN-2158) TestRMWebServicesAppsModification sometimes fails in trunk

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

[jira] [Updated] (YARN-596) Use scheduling policies throughout the queue hierarchy to decide which containers to preempt

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bc Wong updated YARN-596: - Description: In the fair scheduler, containers are chosen for preemption in the following way: All containers

[jira] [Updated] (YARN-2392) add more diags about app retry limits on AM failures

[ https://issues.apache.org/jira/browse/YARN-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-2392: - Attachment: YARN-2392-002.patch patch against migrated git trunk add more diags about app retry

[jira] [Updated] (YARN-2488) Nodemanager should support check if bad disks have turned to good ones

[ https://issues.apache.org/jira/browse/YARN-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xu Yang updated YARN-2488: -- Issue Type: Improvement (was: Bug) Nodemanager should support check if bad disks have turned to good ones

[jira] [Created] (YARN-2488) Nodemanager should support check if bad disks have turned to good ones

Xu Yang created YARN-2488: - Summary: Nodemanager should support check if bad disks have turned to good ones Key: YARN-2488 URL: https://issues.apache.org/jira/browse/YARN-2488 Project: Hadoop YARN

[jira] [Commented] (YARN-2488) Nodemanager should support check if bad disks have turned to good ones

[ https://issues.apache.org/jira/browse/YARN-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118182#comment-14118182 ] Varun Vasudev commented on YARN-2488: - [~yxls123123] will YARN-90 solve your problem?

[jira] [Resolved] (YARN-2488) Nodemanager should support check if bad disks have turned to good ones

[ https://issues.apache.org/jira/browse/YARN-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-2488. -- Resolution: Duplicate This is a duplicate of YARN-90. Nodemanager should support check if bad disks

[jira] [Updated] (YARN-2488) Nodemanager should support check if bad disks have turned to good ones

[ https://issues.apache.org/jira/browse/YARN-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xu Yang updated YARN-2488: -- Affects Version/s: 2.4.1 Nodemanager should support check if bad disks have turned to good ones

[jira] [Commented] (YARN-2392) add more diags about app retry limits on AM failures

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

[jira] [Commented] (YARN-2488) Nodemanager should support check if bad disks have turned to good ones

[ https://issues.apache.org/jira/browse/YARN-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118190#comment-14118190 ] Xu Yang commented on YARN-2488: --- Thank you veryt much, [~vvasudev] and [~jlowe]. It appears

[jira] [Commented] (YARN-90) NodeManager should identify failed disks becoming good back again

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

[jira] [Commented] (YARN-2487) Need to support timeout of AM When no containers are assigned to it for a defined period

[ https://issues.apache.org/jira/browse/YARN-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118228#comment-14118228 ] Steve Loughran commented on YARN-2487: -- link to YARN-624; gang scheduling problem

[jira] [Created] (YARN-2489) ResouceOption's overcommitTimeout should be respected during resource update on NM

Junping Du created YARN-2489: Summary: ResouceOption's overcommitTimeout should be respected during resource update on NM Key: YARN-2489 URL: https://issues.apache.org/jira/browse/YARN-2489 Project:

[jira] [Commented] (YARN-611) Add an AM retry count reset window to YARN RM

[ https://issues.apache.org/jira/browse/YARN-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118378#comment-14118378 ] Vinod Kumar Vavilapalli commented on YARN-611: -- bq. I'm not sure whether it is

[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=14118402#comment-14118402 ] Vinod Kumar Vavilapalli commented on YARN-2448: --- I believe YARN-2463 was

[jira] [Reopened] (YARN-2298) Move TimelineClient to yarn-common project

[ https://issues.apache.org/jira/browse/YARN-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reopened YARN-2298: --- Don't think this is right. The client code should be in, well, the client module.

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118436#comment-14118436 ] Jian He commented on YARN-1372: --- looked at patch YARN-1372.002_NMHandlesCompletedApp, I

[jira] [Updated] (YARN-2468) Log handling for LRS

[ https://issues.apache.org/jira/browse/YARN-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-2468: -- Component/s: log-aggregation Log handling for LRS

[jira] [Commented] (YARN-2468) Log handling for LRS

[ https://issues.apache.org/jira/browse/YARN-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118519#comment-14118519 ] Vinod Kumar Vavilapalli commented on YARN-2468: --- The overall proposal is

[jira] [Updated] (YARN-2284) Find missing config options in YarnConfiguration and yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-2284: - Attachment: YARN-2284-06.patch Move TestMapreduceConfigFields to

[jira] [Commented] (YARN-2033) Investigate merging generic-history into the Timeline Store

[ https://issues.apache.org/jira/browse/YARN-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118563#comment-14118563 ] Vinod Kumar Vavilapalli commented on YARN-2033: --- Having a quick look at

[jira] [Commented] (YARN-2394) FairScheduler: Configure fairSharePreemptionThreshold per queue

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

[jira] [Commented] (YARN-2306) leak of reservation metrics (fair scheduler)

[ https://issues.apache.org/jira/browse/YARN-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118617#comment-14118617 ] Ashwin Shankar commented on YARN-2306: -- [~kasha], we saw reservation metrics leak in

[jira] [Commented] (YARN-2284) Find missing config options in YarnConfiguration and yarn-default.xml

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

[jira] [Updated] (YARN-1530) [Umbrella] Store, manage and serve per-framework application-timeline data

[ https://issues.apache.org/jira/browse/YARN-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-1530: -- Attachment: ATS-meet-up-8-28-2014-notes.pdf Some members of the Hadoop open source community that are

[jira] [Commented] (YARN-2298) Move TimelineClient to yarn-common project

[ https://issues.apache.org/jira/browse/YARN-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118679#comment-14118679 ] Vinod Kumar Vavilapalli commented on YARN-2298: --- Marking it as a blocker for

[jira] [Commented] (YARN-2284) Find missing config options in YarnConfiguration and yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118681#comment-14118681 ] Ray Chiang commented on YARN-2284: -- RE: Test

[jira] [Commented] (YARN-2306) leak of reservation metrics (fair scheduler)

[ https://issues.apache.org/jira/browse/YARN-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118683#comment-14118683 ] Karthik Kambatla commented on YARN-2306: The patch doesn't apply to trunk anymore.

[jira] [Commented] (YARN-415) Capture aggregate memory allocation at the app-level for chargeback

[ https://issues.apache.org/jira/browse/YARN-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118707#comment-14118707 ] Karthik Kambatla commented on YARN-415: --- Looking at the patch now, sorry for the

[jira] [Commented] (YARN-415) Capture aggregate memory allocation at the app-level for chargeback

[ https://issues.apache.org/jira/browse/YARN-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118713#comment-14118713 ] Karthik Kambatla commented on YARN-415: --- The patch doesn't apply anymore, due to

[jira] [Commented] (YARN-415) Capture aggregate memory allocation at the app-level for chargeback

[ https://issues.apache.org/jira/browse/YARN-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118757#comment-14118757 ] Karthik Kambatla commented on YARN-415: --- Patch looks pretty clean and mostly good.

[jira] [Updated] (YARN-2229) ContainerId can overflow with RM restart

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2229: - Attachment: YARN-2229.13.patch Updated a patch to use getContainerId() in compareTo and equals.

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

[ https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-2056: - Attachment: YARN-2056.201409022208.txt Thanks very much, [~leftnoteasy]. I have added the test for

[jira] [Commented] (YARN-2229) ContainerId can overflow with RM restart

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118931#comment-14118931 ] Hadoop QA commented on YARN-2229: - {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=14118954#comment-14118954 ] Hadoop QA commented on YARN-2056: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2327) YARN should warn about nodes with poor clock synchronization

[ https://issues.apache.org/jira/browse/YARN-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14118978#comment-14118978 ] Colin Patrick McCabe commented on YARN-2327: Thanks, Vinod, that's pretty

[jira] [Updated] (YARN-1779) Handle AMRMTokens across RM failover

[ https://issues.apache.org/jira/browse/YARN-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1779: -- Target Version/s: 2.6.0 (was: 2.4.0) Handle AMRMTokens across RM failover

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14118995#comment-14118995 ] Jian He commented on YARN-2404: --- Tsuyoshi, thanks for your effort on this issue ! I looked

[jira] [Created] (YARN-2490) Bad links to jobhistory server

Todd Lipcon created YARN-2490: - Summary: Bad links to jobhistory server Key: YARN-2490 URL: https://issues.apache.org/jira/browse/YARN-2490 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-1492) truly shared cache for jars (jobjar/libjar)

[ https://issues.apache.org/jira/browse/YARN-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated YARN-1492: --- Attachment: YARN-1492-all-trunk-v4.patch Rebase and addressing HadoopQA warnings. truly shared cache

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

[ https://issues.apache.org/jira/browse/YARN-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subramaniam Krishnan updated YARN-1707: --- Attachment: YARN-1707.6.patch Thanks [~jianhe] for your feedback. I am uploading a new

[jira] [Commented] (YARN-611) Add an AM retry count reset window to YARN RM

[ https://issues.apache.org/jira/browse/YARN-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14119191#comment-14119191 ] Vinod Kumar Vavilapalli commented on YARN-611: -- bq. 1. API Change: I'm not sure

[jira] [Commented] (YARN-90) NodeManager should identify failed disks becoming good back again

[ https://issues.apache.org/jira/browse/YARN-90?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14119194#comment-14119194 ] Xu Yang commented on YARN-90: - Hi, [~vvasudev]. Thanks a lot for your patch. Is it finished? I

[jira] [Created] (YARN-2491) Speculative attempts should not run on the same node as their original attempt

Todd Lipcon created YARN-2491: - Summary: Speculative attempts should not run on the same node as their original attempt Key: YARN-2491 URL: https://issues.apache.org/jira/browse/YARN-2491 Project: Hadoop

[jira] [Commented] (YARN-796) Allow for (admin) labels on nodes and resource-requests

[ https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14119233#comment-14119233 ] Viplav Madasu commented on YARN-796: Hi Wangda, I was looking into your patch and

[jira] [Updated] (YARN-2229) ContainerId can overflow with RM restart

[ https://issues.apache.org/jira/browse/YARN-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-2229: - Attachment: YARN-2229.14.patch Updated to pass tests and use getContainerId in ContainerId#equals

[jira] [Updated] (YARN-2306) leak of reservation metrics (fair scheduler)

[ https://issues.apache.org/jira/browse/YARN-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hong Zhiguo updated YARN-2306: -- Attachment: YARN-2306-2.patch updated the patch with only the new unit test, since it seems this bug is

[jira] [Commented] (YARN-2394) FairScheduler: Configure fairSharePreemptionThreshold per queue

[ https://issues.apache.org/jira/browse/YARN-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14119278#comment-14119278 ] Ashwin Shankar commented on YARN-2394: -- [~ywskycn], patch looks almost good. Couple of

[jira] [Commented] (YARN-1492) truly shared cache for jars (jobjar/libjar)

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

[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 ] Tsuyoshi OZAWA updated YARN-2404: - Attachment: YARN-2404.3.patch Jian, thanks for your review. Updated a patch to address your

[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=14119355#comment-14119355 ] Hadoop QA commented on YARN-1707: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-2306) leak of reservation metrics (fair scheduler)

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

[jira] [Commented] (YARN-2394) FairScheduler: Configure fairSharePreemptionThreshold per queue

[ https://issues.apache.org/jira/browse/YARN-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14119379#comment-14119379 ] Ashwin Shankar commented on YARN-2394: -- Also, a subjective opinion(feel free to ignore