[jira] [Commented] (YARN-1607) TestRM expects the capacity scheduler

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

[jira] [Commented] (YARN-1611) Make admin refresh* s work for both Active RM and Standby RM

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

[jira] [Commented] (YARN-1616) RMFatalEventDispatcher should log the cause of the event

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

[jira] [Commented] (YARN-1616) RMFatalEventDispatcher should log the cause of the event

[ https://issues.apache.org/jira/browse/YARN-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877453#comment-13877453 ] Hudson commented on YARN-1616: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1676 (See [htt

[jira] [Commented] (YARN-1616) RMFatalEventDispatcher should log the cause of the event

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

[jira] [Updated] (YARN-925) Augment HistoryStorage Reader Interface to Support Filters When Getting Applications

[ https://issues.apache.org/jira/browse/YARN-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichi Yamashita updated YARN-925: Attachment: YARN-925-7.patch Based on the former discussion, I attach a patch applying a filt

[jira] [Commented] (YARN-1618) ZKRMStateStore fails to handle updates to znodes not yet created

[ https://issues.apache.org/jira/browse/YARN-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877582#comment-13877582 ] Karthik Kambatla commented on YARN-1618: Thanks Bikas. Looks like the transitions h

[jira] [Assigned] (YARN-1612) Change Fair Scheduler to not disable delay scheduling by default

[ https://issues.apache.org/jira/browse/YARN-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He reassigned YARN-1612: - Assignee: Chen He > Change Fair Scheduler to not disable delay scheduling by default > ---

[jira] [Commented] (YARN-1618) ZKRMStateStore fails to handle updates to znodes not yet created

[ https://issues.apache.org/jira/browse/YARN-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877599#comment-13877599 ] Karthik Kambatla commented on YARN-1618: >From the transitions in RMAppImpl, it loo

[jira] [Updated] (YARN-1618) Applications transition from NEW to FINAL_SAVING, and try to update non-existing entries in the state-store

[ https://issues.apache.org/jira/browse/YARN-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1618: --- Summary: Applications transition from NEW to FINAL_SAVING, and try to update non-existing entr

[jira] [Updated] (YARN-1561) Fix a generic type warning in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-1561: -- Attachment: yarn-1561.patch > Fix a generic type warning in FairScheduler >

[jira] [Assigned] (YARN-1561) Fix a generic type warning in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He reassigned YARN-1561: - Assignee: Chen He > Fix a generic type warning in FairScheduler >

[jira] [Updated] (YARN-1618) Applications transition from NEW to FINAL_SAVING, and try to update non-existing entries in the state-store

[ https://issues.apache.org/jira/browse/YARN-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1618: --- Description: YARN-891 augments the RMStateStore to store information on completed application

[jira] [Updated] (YARN-1618) Applications transition from NEW to FINAL_SAVING, and try to update non-existing entries in the state-store

[ https://issues.apache.org/jira/browse/YARN-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1618: --- Priority: Blocker (was: Critical) > Applications transition from NEW to FINAL_SAVING, and try

[jira] [Commented] (YARN-1607) TestRM expects the capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877643#comment-13877643 ] Karthik Kambatla commented on YARN-1607: Not introduced by this patch, but the whil

[jira] [Commented] (YARN-1611) Make admin refresh* s work for both Active RM and Standby RM

[ https://issues.apache.org/jira/browse/YARN-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877645#comment-13877645 ] Xuan Gong commented on YARN-1611: - test case failure is un-related, and it passed locally.

[jira] [Commented] (YARN-1618) Applications transition from NEW to FINAL_SAVING, and try to update non-existing entries in the state-store

[ https://issues.apache.org/jira/browse/YARN-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877681#comment-13877681 ] Bikas Saha commented on YARN-1618: -- Unless NEW->FINAL_SAVING upon failure, was added by a

[jira] [Created] (YARN-1619) Add cli to kill yarn container

Ramya Sunil created YARN-1619: - Summary: Add cli to kill yarn container Key: YARN-1619 URL: https://issues.apache.org/jira/browse/YARN-1619 Project: Hadoop YARN Issue Type: Improvement

[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=13877716#comment-13877716 ] Xuan Gong commented on YARN-1525: - [~cindy2012] Comments: * Looks like the web service does

[jira] [Commented] (YARN-1561) Fix a generic type warning in FairScheduler

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

[jira] [Created] (YARN-1620) Add cli to simulate app failure in yarn container

Tassapol Athiapinya created YARN-1620: - Summary: Add cli to simulate app failure in yarn container Key: YARN-1620 URL: https://issues.apache.org/jira/browse/YARN-1620 Project: Hadoop YARN

[jira] [Commented] (YARN-1607) TestRM expects the capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877766#comment-13877766 ] Sandy Ryza commented on YARN-1607: -- For the timeouts, I think the cleanest would be to add

[jira] [Updated] (YARN-1619) Add cli to kill yarn container

[ https://issues.apache.org/jira/browse/YARN-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1619: -- Issue Type: New Feature (was: Improvement) > Add cli to kill yarn container > -

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

Tassapol Athiapinya created YARN-1621: - Summary: Add CLI to list states of yarn container-IDs/hosts Key: YARN-1621 URL: https://issues.apache.org/jira/browse/YARN-1621 Project: Hadoop YARN

[jira] [Commented] (YARN-1619) Add cli to kill yarn container

[ https://issues.apache.org/jira/browse/YARN-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877769#comment-13877769 ] Gera Shegalov commented on YARN-1619: - +1 for this feature especially in connection wit

[jira] [Resolved] (YARN-1620) Add cli to simulate app failure in yarn container

[ https://issues.apache.org/jira/browse/YARN-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1620. --- Resolution: Duplicate > Add cli to simulate app failure in yarn container > --

[jira] [Updated] (YARN-1607) TestRM expects the capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1607: - Attachment: YARN-1607-1.patch > TestRM expects the capacity scheduler > --

[jira] [Commented] (YARN-1607) TestRM expects the capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877801#comment-13877801 ] Karthik Kambatla commented on YARN-1607: Looks mostly good. One more nit: instead o

[jira] [Commented] (YARN-1607) TestRM expects the capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877803#comment-13877803 ] Karthik Kambatla commented on YARN-1607: I don't know the reason why, but I was tol

[jira] [Commented] (YARN-1607) TestRM expects the capacity scheduler

[ https://issues.apache.org/jira/browse/YARN-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877804#comment-13877804 ] Karthik Kambatla commented on YARN-1607: I do agree timeouts are the easiest way to

[jira] [Commented] (YARN-1561) Fix a generic type warning in FairScheduler

[ https://issues.apache.org/jira/browse/YARN-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877811#comment-13877811 ] Chen He commented on YARN-1561: --- To fix this warning, we specify the generic type of this com

[jira] [Updated] (YARN-1617) Remove ancient comment and surround LOG.debug in AppSchedulingInfo.allocate

[ https://issues.apache.org/jira/browse/YARN-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1617: - Attachment: YARN-1617.patch > Remove ancient comment and surround LOG.debug in AppSchedulingInfo.allocate

[jira] [Commented] (YARN-1617) Remove ancient comment and surround LOG.debug in AppSchedulingInfo.allocate

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

[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=13877921#comment-13877921 ] Cindy Li commented on YARN-1525: Xuan, did you apply patch v1 or v2 for testing it? > We

[jira] [Created] (YARN-1622) 'yarn' command doesn't behave like 'hadoop' and etc.

Mohammad Kamrul Islam created YARN-1622: --- Summary: 'yarn' command doesn't behave like 'hadoop' and etc. Key: YARN-1622 URL: https://issues.apache.org/jira/browse/YARN-1622 Project: Hadoop YARN

[jira] [Updated] (YARN-1622) 'bin/yarn' command doesn't behave like 'hadoop' and etc.

[ https://issues.apache.org/jira/browse/YARN-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Kamrul Islam updated YARN-1622: Affects Version/s: 2.2.0 Summary: 'bin/yarn' command doesn't behave lik

[jira] [Created] (YARN-1623) Include queue name in RegisterApplicationMasterResponse

Sandy Ryza created YARN-1623: Summary: Include queue name in RegisterApplicationMasterResponse Key: YARN-1623 URL: https://issues.apache.org/jira/browse/YARN-1623 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-1622) 'bin/yarn' command doesn't behave like 'hadoop' and etc.

[ https://issues.apache.org/jira/browse/YARN-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878118#comment-13878118 ] Mohammad Kamrul Islam commented on YARN-1622: - Further analysis found the some

[jira] [Updated] (YARN-1623) Include queue name in RegisterApplicationMasterResponse

[ https://issues.apache.org/jira/browse/YARN-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-1623: - Attachment: YARN-1623.patch > Include queue name in RegisterApplicationMasterResponse > --

[jira] [Created] (YARN-1624) QueuePlacementPolicy format is not easily readable via a JAXB parser

Aditya Acharya created YARN-1624: Summary: QueuePlacementPolicy format is not easily readable via a JAXB parser Key: YARN-1624 URL: https://issues.apache.org/jira/browse/YARN-1624 Project: Hadoop YARN

[jira] [Updated] (YARN-1624) QueuePlacementPolicy format is not easily readable via a JAXB parser

[ https://issues.apache.org/jira/browse/YARN-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aditya Acharya updated YARN-1624: - Attachment: diff.txt Patch that solves the problem. > QueuePlacementPolicy format is not easily r

[jira] [Commented] (YARN-1624) QueuePlacementPolicy format is not easily readable via a JAXB parser

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

[jira] [Commented] (YARN-1624) QueuePlacementPolicy format is not easily readable via a JAXB parser

[ https://issues.apache.org/jira/browse/YARN-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878193#comment-13878193 ] Sandy Ryza commented on YARN-1624: -- +1 > QueuePlacementPolicy format is not easily readab

[jira] [Assigned] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenji Kikushima reassigned YARN-1480: - Assignee: Kenji Kikushima > RM web services getApps() accepts many more filters than Appli

[jira] [Updated] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenji Kikushima updated YARN-1480: -- Attachment: YARN-1480.patch Added other RM web service filters to ApplicationCLI. Concretely: fi

[jira] [Commented] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

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

[jira] [Commented] (YARN-1617) Remove ancient comment and surround LOG.debug in AppSchedulingInfo.allocate

[ https://issues.apache.org/jira/browse/YARN-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878299#comment-13878299 ] Akira AJISAKA commented on YARN-1617: - LGTM, +1. I think the refactoring does not need

[jira] [Updated] (YARN-1617) Remove ancient comment and surround LOG.debug in AppSchedulingInfo.allocate

[ https://issues.apache.org/jira/browse/YARN-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-1617: Hadoop Flags: Reviewed > Remove ancient comment and surround LOG.debug in AppSchedulingInfo.allocate

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13878308#comment-13878308 ] Andrey Klochkov commented on YARN-415: -- I'm updating the patch to make it applicable to

[jira] [Commented] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878312#comment-13878312 ] Akira AJISAKA commented on YARN-1480: - [~kj-ki], thank you for taking this! Would you a

[jira] [Commented] (YARN-1480) RM web services getApps() accepts many more filters than ApplicationCLI "list" command

[ https://issues.apache.org/jira/browse/YARN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13878314#comment-13878314 ] Akira AJISAKA commented on YARN-1480: - Link to YARN-1531 for command line documentation

[jira] [Updated] (YARN-925) Augment HistoryStorage Reader Interface to Support Filters When Getting Applications

[ https://issues.apache.org/jira/browse/YARN-925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shinichi Yamashita updated YARN-925: Attachment: YARN-925-8.patch I confirmed that the former patch had some wrong codes. I attach

[jira] [Commented] (YARN-925) Augment HistoryStorage Reader Interface to Support Filters When Getting Applications

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