[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

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

[jira] [Commented] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867591#comment-13867591 ] Xuan Gong commented on YARN-1410: - Posting a patch that outlines the approach. Thanks to th

[jira] [Updated] (YARN-1410) Handle client failover during 2 step client API's like app submission

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1410: Attachment: YARN-1410-outline.patch > Handle client failover during 2 step client API's like app submission

[jira] [Updated] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1490: -- Attachment: YARN-1490.11.patch submit the same patch to kick jenkins > RM should optionally not kill all contai

[jira] [Commented] (YARN-1583) Ineffective state check in FairSchedulerAppsBlock#render()

[ https://issues.apache.org/jira/browse/YARN-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867556#comment-13867556 ] Bangtao Zhou commented on YARN-1583: I am checking on **branch-2.2.0**, and I just che

[jira] [Commented] (YARN-1166) YARN 'appsFailed' metric should be of type 'counter'

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

[jira] [Commented] (YARN-888) clean up POM dependencies

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

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

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

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867488#comment-13867488 ] Alejandro Abdelnur commented on YARN-888: - [~vinodkv], thx for taking the time to p

[jira] [Updated] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated YARN-888: Attachment: YARN-888.patch > clean up POM dependencies > - > >

[jira] [Updated] (YARN-1166) YARN 'appsFailed' metric should be of type 'counter'

[ https://issues.apache.org/jira/browse/YARN-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1166: -- Attachment: YARN-1166.8.patch Thanks Vinod and Jian for your review. I uploaded a new patch. bq. One co

[jira] [Commented] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867484#comment-13867484 ] Xuan Gong commented on YARN-1033: - +1 LGTM > Expose RM active/standby state to Web UI and

[jira] [Updated] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1574: Attachment: YARN-1574.5.patch > When RM transit from Active to Standby, the same eventDispatcher should not

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867473#comment-13867473 ] Xuan Gong commented on YARN-1574: - bq. I should have thought of this earlier - we should re

[jira] [Commented] (YARN-1583) Ineffective state check in FairSchedulerAppsBlock#render()

[ https://issues.apache.org/jira/browse/YARN-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867472#comment-13867472 ] Ted Yu commented on YARN-1583: -- I was looking at this class in trunk. I don't see the above co

[jira] [Commented] (YARN-1583) Ineffective state check in FairSchedulerAppsBlock#render()

[ https://issues.apache.org/jira/browse/YARN-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867466#comment-13867466 ] Bangtao Zhou commented on YARN-1583: Line #84 {code}reqAppStates = new HashSet(appStat

[jira] [Commented] (YARN-1496) Protocol additions to allow moving apps between queues

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

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

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

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

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

[jira] [Updated] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1490: -- Attachment: YARN-1490.11.patch > RM should optionally not kill all containers when an ApplicationMaster exits >

[jira] [Commented] (YARN-1506) Replace set resource change on RMNode/SchedulerNode directly with event notification.

[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867424#comment-13867424 ] Junping Du commented on YARN-1506: -- Thank you, Bikas! > Replace set resource change on RM

[jira] [Updated] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1490: -- Attachment: YARN-1490.10.patch fix the find bug > RM should optionally not kill all containers when an Applicat

[jira] [Commented] (YARN-1525) Web UI should redirect to active RM when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867420#comment-13867420 ] Cindy Li commented on YARN-1525: Ok. I'll try to accommodate the change in YARN-1033. > W

[jira] [Commented] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867413#comment-13867413 ] Nemon Lou commented on YARN-1033: - Thanks Karthik Kambatla .You are really efficient. +1(no

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867412#comment-13867412 ] Vinod Kumar Vavilapalli commented on YARN-888: -- Playing with the patch. hadoop

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

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

[jira] [Updated] (YARN-1496) Protocol additions to allow moving apps between queues

[ https://issues.apache.org/jira/browse/YARN-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1496: - Attachment: YARN-1496-6.patch > Protocol additions to allow moving apps between queues > -

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

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

[jira] [Updated] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1490: -- Attachment: YARN-1490.9.patch Fixed one test name in TestRMAppAttemptTransitions > RM should optionally not kil

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867386#comment-13867386 ] Jian He commented on YARN-1490: --- - New patch got rid of the local flag transferStateFromPrevi

[jira] [Commented] (YARN-1579) ActiveRMInfoProto fields should be optional

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

[jira] [Updated] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1490: -- Attachment: YARN-1490.8.patch > RM should optionally not kill all containers when an ApplicationMaster exits > -

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867371#comment-13867371 ] Karthik Kambatla commented on YARN-1574: Yes. Indeed. > When RM transit from Acti

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867366#comment-13867366 ] Xuan Gong commented on YARN-1574: - [~kkambatl] bq. I also noticed CompositeService#removeSe

[jira] [Commented] (YARN-1399) Allow users to annotate an application with multiple tags

[ https://issues.apache.org/jira/browse/YARN-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867362#comment-13867362 ] Karthik Kambatla commented on YARN-1399: [~vinodkv], [~sandyr] - do we agree on set

[jira] [Updated] (YARN-1579) ActiveRMInfoProto fields should be optional

[ https://issues.apache.org/jira/browse/YARN-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1579: --- Priority: Trivial (was: Major) > ActiveRMInfoProto fields should be optional > --

[jira] [Commented] (YARN-1506) Replace set resource change on RMNode/SchedulerNode directly with event notification.

[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867355#comment-13867355 ] Bikas Saha commented on YARN-1506: -- I will get to this by the weekend. Sorry for the delay

[jira] [Commented] (YARN-1579) ActiveRMInfoProto fields should be optional

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

[jira] [Commented] (YARN-1496) Protocol additions to allow moving apps between queues

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

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

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

[jira] [Commented] (YARN-1506) Replace set resource change on RMNode/SchedulerNode directly with event notification.

[ https://issues.apache.org/jira/browse/YARN-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867315#comment-13867315 ] Junping Du commented on YARN-1506: -- bq. Patch looks good to me mostly, Bikas Saha/ Vinod K

[jira] [Updated] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1490: -- Attachment: YARN-1490.7.patch > RM should optionally not kill all containers when an ApplicationMaster exits > -

[jira] [Commented] (YARN-1525) Web UI should redirect to active RM when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867294#comment-13867294 ] Karthik Kambatla commented on YARN-1525: I am sorry if I came out wrong, I do see m

[jira] [Commented] (YARN-1496) Protocol additions to allow moving apps between queues

[ https://issues.apache.org/jira/browse/YARN-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867293#comment-13867293 ] Sandy Ryza commented on YARN-1496: -- Thought ChangeApplicationQueue would be better because

[jira] [Updated] (YARN-1496) Protocol additions to allow moving apps between queues

[ https://issues.apache.org/jira/browse/YARN-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1496: - Attachment: YARN-1496-5.patch > Protocol additions to allow moving apps between queues > -

[jira] [Commented] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867283#comment-13867283 ] Karthik Kambatla commented on YARN-1033: Thanks Sandy. I ll commit this tomorrow mo

[jira] [Commented] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867281#comment-13867281 ] Sandy Ryza commented on YARN-1033: -- +1 > Expose RM active/standby state to Web UI and RES

[jira] [Commented] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867280#comment-13867280 ] Karthik Kambatla commented on YARN-1033: Deployed a psuedo-dist cluster, verified o

[jira] [Updated] (YARN-1579) ActiveRMInfoProto fields should be optional

[ https://issues.apache.org/jira/browse/YARN-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1579: --- Attachment: yarn-1579-1.patch Uploading the same patch again. > ActiveRMInfoProto fields sho

[jira] [Commented] (YARN-1138) yarn.application.classpath is set to point to $HADOOP_CONF_DIR etc., which does not work on Windows

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

[jira] [Created] (YARN-1583) Ineffective state check in FairSchedulerAppsBlock#render()

Ted Yu created YARN-1583: Summary: Ineffective state check in FairSchedulerAppsBlock#render() Key: YARN-1583 URL: https://issues.apache.org/jira/browse/YARN-1583 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-1033) Expose RM active/standby state to Web UI and REST API

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

[jira] [Commented] (YARN-1579) ActiveRMInfoProto fields should be optional

[ https://issues.apache.org/jira/browse/YARN-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867265#comment-13867265 ] Sandy Ryza commented on YARN-1579: -- +1 > ActiveRMInfoProto fields should be optional > --

[jira] [Commented] (YARN-1579) ActiveRMInfoProto fields should be optional

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

[jira] [Commented] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867262#comment-13867262 ] Sandy Ryza commented on YARN-1567: -- bq. Didn't say that we should stop this. If we are doi

[jira] [Commented] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867254#comment-13867254 ] Karthik Kambatla commented on YARN-1033: The posted patch doesn't add the informati

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867248#comment-13867248 ] Vinod Kumar Vavilapalli commented on YARN-888: -- Yeah. I can see that. Either wa

[jira] [Updated] (YARN-1579) ActiveRMInfoProto fields should be optional

[ https://issues.apache.org/jira/browse/YARN-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1579: --- Attachment: yarn-1579-1.patch Trivial patch that modifies the fields to optional. > ActiveRM

[jira] [Commented] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867219#comment-13867219 ] Vinod Kumar Vavilapalli commented on YARN-1567: --- bq. I don't think that we sh

[jira] [Updated] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1033: --- Description: Both active and standby RM shall expose it's web server and show it's current sta

[jira] [Resolved] (YARN-1581) Fair Scheduler: containers that get reserved create container token to early

[ https://issues.apache.org/jira/browse/YARN-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1581. --- Resolution: Duplicate Duplicate of YARN-1417. > Fair Scheduler: containers th

[jira] [Updated] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1033: --- Attachment: yarn-1033-1.patch Straight-forward patch that adds the HA state information to Clu

[jira] [Updated] (YARN-1033) Expose RM active/standby state to Web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1033: --- Summary: Expose RM active/standby state to Web UI and REST API (was: Expose RM active/standby

[jira] [Created] (YARN-1582) Capacity Scheduler: add a maximum-allocation-mb setting per queue

Thomas Graves created YARN-1582: --- Summary: Capacity Scheduler: add a maximum-allocation-mb setting per queue Key: YARN-1582 URL: https://issues.apache.org/jira/browse/YARN-1582 Project: Hadoop YARN

[jira] [Commented] (YARN-1041) Protocol changes for RM to bind and notify a restarted AM of existing containers

[ https://issues.apache.org/jira/browse/YARN-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867184#comment-13867184 ] Vinod Kumar Vavilapalli commented on YARN-1041: --- Knowing well this is an earl

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867169#comment-13867169 ] Karthik Kambatla commented on YARN-1574: The test looks much cleaner now. I shoul

[jira] [Commented] (YARN-1138) yarn.application.classpath is set to point to $HADOOP_CONF_DIR etc., which does not work on Windows

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

[jira] [Commented] (YARN-650) User guide for preemption

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

[jira] [Commented] (YARN-1525) Web UI should redirect to active RM when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867022#comment-13867022 ] Cindy Li commented on YARN-1525: @Karthik Kambatla, I'm proposing the following. From a use

[jira] [Commented] (YARN-1525) Web UI should redirect to active RM when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867004#comment-13867004 ] Cindy Li commented on YARN-1525: I've been thinking about the best way to find the current

[jira] [Commented] (YARN-1525) Web UI should redirect to active RM when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867002#comment-13867002 ] Karthik Kambatla commented on YARN-1525: Thinking out loud: Given that YARN-1482

[jira] [Commented] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

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

[jira] [Updated] (YARN-1490) RM should optionally not kill all containers when an ApplicationMaster exits

[ https://issues.apache.org/jira/browse/YARN-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1490: -- Attachment: YARN-1490.6.patch New patch added the test for testing reserved container to be killed by the previ

[jira] [Updated] (YARN-1525) Web UI should redirect to active RM when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cindy Li updated YARN-1525: --- Assignee: Cindy Li (was: Xuan Gong) > Web UI should redirect to active RM when HA is enabled. > -

[jira] [Updated] (YARN-780) Expose preemption warnings in AMRMClient

[ https://issues.apache.org/jira/browse/YARN-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-780: - Issue Type: Sub-task (was: Improvement) Parent: YARN-45 > Expose preemptio

[jira] [Updated] (YARN-650) User guide for preemption

[ https://issues.apache.org/jira/browse/YARN-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-650: - Issue Type: Sub-task (was: Task) Parent: YARN-45 > User guide for preempti

[jira] [Updated] (YARN-568) FairScheduler: support for work-preserving preemption

[ https://issues.apache.org/jira/browse/YARN-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-568: - Issue Type: Sub-task (was: Improvement) Parent: YARN-45 > FairScheduler: s

[jira] [Updated] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-569: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-397) > CapacitySche

[jira] [Updated] (YARN-569) CapacityScheduler: support for preemption (using a capacity monitor)

[ https://issues.apache.org/jira/browse/YARN-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-569: - Issue Type: Sub-task (was: Bug) Parent: YARN-45 > CapacityScheduler: suppo

[jira] [Updated] (YARN-567) RM changes to support preemption for FairScheduler and CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-567: - Issue Type: Bug (was: Sub-task) Parent: (was: YARN-397) > RM changes t

[jira] [Updated] (YARN-567) RM changes to support preemption for FairScheduler and CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-567: - Issue Type: Sub-task (was: Bug) Parent: YARN-45 > RM changes to support pr

[jira] [Updated] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-45: Issue Type: Bug (was: Sub-task) Parent: (was: YARN-397) > Scheduler feedb

[jira] [Updated] (YARN-1138) yarn.application.classpath is set to point to $HADOOP_CONF_DIR etc., which does not work on Windows

[ https://issues.apache.org/jira/browse/YARN-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Nauroth updated YARN-1138: Component/s: api Target Version/s: 3.0.0, 2.3.0 Affects Version/s: 2.2.0 Fix V

[jira] [Updated] (YARN-1138) yarn.application.classpath is set to point to $HADOOP_CONF_DIR etc., which does not work on Windows

[ https://issues.apache.org/jira/browse/YARN-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuan Liu updated YARN-1138: Attachment: YARN-1138.2.patch Sound good! Here is new patch that addressed the two issues. > yarn.applicati

[jira] [Commented] (YARN-915) Apps Completed metrics on web UI is not correct after RM restart

[ https://issues.apache.org/jira/browse/YARN-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866972#comment-13866972 ] Jian He commented on YARN-915: -- closed as a duplicate of YARN-1166 > Apps Completed metrics on

[jira] [Resolved] (YARN-915) Apps Completed metrics on web UI is not correct after RM restart

[ https://issues.apache.org/jira/browse/YARN-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He resolved YARN-915. -- Resolution: Duplicate > Apps Completed metrics on web UI is not correct after RM restart > --

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866945#comment-13866945 ] Alejandro Abdelnur commented on YARN-888: - You got it. On the hybrid approach, it is

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866925#comment-13866925 ] Vinod Kumar Vavilapalli commented on YARN-888: -- Further, may be we should also

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866923#comment-13866923 ] Vinod Kumar Vavilapalli commented on YARN-888: -- Makes sense now. I think I unde

[jira] [Commented] (YARN-1576) Allow setting RPC timeout in ApplicationClientProtocolPBClientImpl

[ https://issues.apache.org/jira/browse/YARN-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866889#comment-13866889 ] Sandy Ryza commented on YARN-1576: -- This tracks the YARN changes that will be necessary fo

[jira] [Commented] (YARN-1576) Allow setting RPC timeout in ApplicationClientProtocolPBClientImpl

[ https://issues.apache.org/jira/browse/YARN-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866887#comment-13866887 ] Chris Nauroth commented on YARN-1576: - Duplicate of MAPREDUCE-5707? (Or possibly worth

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

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

[jira] [Commented] (YARN-1567) In Fair Scheduler, allow empty queues to change between leaf and parent on allocation file reload

[ https://issues.apache.org/jira/browse/YARN-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866877#comment-13866877 ] Sandy Ryza commented on YARN-1567: -- The Fair Scheduler does not have a notion of stopped q

[jira] [Commented] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866855#comment-13866855 ] Xuan Gong commented on YARN-1574: - Thanks for the review. The new patch addresses all the l

[jira] [Updated] (YARN-1574) When RM transit from Active to Standby, the same eventDispatcher should not be registered more than once

[ https://issues.apache.org/jira/browse/YARN-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1574: Attachment: YARN-1574.4.patch > When RM transit from Active to Standby, the same eventDispatcher should not

[jira] [Comment Edited] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866845#comment-13866845 ] Alejandro Abdelnur edited comment on YARN-888 at 1/9/14 5:50 PM: -

[jira] [Commented] (YARN-1138) yarn.application.classpath is set to point to $HADOOP_CONF_DIR etc., which does not work on Windows

[ https://issues.apache.org/jira/browse/YARN-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866848#comment-13866848 ] Chris Nauroth commented on YARN-1138: - Hi, Chuan. The patch looks good. It's a simila

[jira] [Commented] (YARN-888) clean up POM dependencies

[ https://issues.apache.org/jira/browse/YARN-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866845#comment-13866845 ] Alejandro Abdelnur commented on YARN-888: - [~vinodvk], While having dependencies i

[jira] [Commented] (YARN-1413) [YARN-321] AHS WebUI should server aggregated logs as well

[ https://issues.apache.org/jira/browse/YARN-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866844#comment-13866844 ] Zhijie Shen commented on YARN-1413: --- Checked RMContainerImpl again. It's wrong to set lo

[jira] [Updated] (YARN-1581) Fair Scheduler: containers that get reserved create container token to early

[ https://issues.apache.org/jira/browse/YARN-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] German Florez-Larrahondo updated YARN-1581: --- Attachment: (was: ProcessInfo construction failing.jpg) > Fair Scheduler:

  1   2   >