[jira] [Commented] (YARN-1768) yarn kill non-existent application is too verbose

[ https://issues.apache.org/jira/browse/YARN-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920667#comment-13920667 ] Tsuyoshi OZAWA commented on YARN-1768: -- Thank you for the review, [~raviprak]! I ran

[jira] [Commented] (YARN-1389) ApplicationClientProtocol and ApplicationHistoryProtocol should expose analogous APIs

[ https://issues.apache.org/jira/browse/YARN-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920669#comment-13920669 ] Mayank Bansal commented on YARN-1389: - Thanks [~zjshen] for the review. bq. 1. I still

[jira] [Updated] (YARN-1389) ApplicationClientProtocol and ApplicationHistoryProtocol should expose analogous APIs

[ https://issues.apache.org/jira/browse/YARN-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-1389: Attachment: YARN-1389-4.patch Attaching latest patch. Thanks, Mayank ApplicationClientProtocol

[jira] [Commented] (YARN-1768) yarn kill non-existent application is too verbose

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

[jira] [Commented] (YARN-1768) yarn kill non-existent application is too verbose

[ https://issues.apache.org/jira/browse/YARN-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920703#comment-13920703 ] Ravi Prakash commented on YARN-1768: https://issues.apache.org/jira/browse/YARN-1657 is

[jira] [Updated] (YARN-1768) yarn kill non-existent application is too verbose

[ https://issues.apache.org/jira/browse/YARN-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-1768: --- Fix Version/s: 2.4.0 yarn kill non-existent application is too verbose

[jira] [Commented] (YARN-1781) NM should allow users to specify max disk utilization for local disks

[ https://issues.apache.org/jira/browse/YARN-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13920735#comment-13920735 ] Sunil G commented on YARN-1781: --- Thank you for the reply. I have another point in addition to

[jira] [Commented] (YARN-986) RM DT token service should have service addresses of both RMs

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

[jira] [Commented] (YARN-1730) Leveldb timeline store needs simple write locking

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

[jira] [Commented] (YARN-1766) When RM does the initiation, it should use loaded Configuration instead of bootstrap configuration.

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

[jira] [Commented] (YARN-1389) ApplicationClientProtocol and ApplicationHistoryProtocol should expose analogous APIs

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

[jira] [Commented] (YARN-986) RM DT token service should have service addresses of both RMs

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

[jira] [Commented] (YARN-1730) Leveldb timeline store needs simple write locking

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

[jira] [Commented] (YARN-1766) When RM does the initiation, it should use loaded Configuration instead of bootstrap configuration.

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

[jira] [Commented] (YARN-1768) yarn kill non-existent application is too verbose

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

[jira] [Commented] (YARN-1730) Leveldb timeline store needs simple write locking

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

[jira] [Commented] (YARN-1766) When RM does the initiation, it should use loaded Configuration instead of bootstrap configuration.

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

[jira] [Commented] (YARN-986) RM DT token service should have service addresses of both RMs

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

[jira] [Commented] (YARN-1768) yarn kill non-existent application is too verbose

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

[jira] [Updated] (YARN-1781) NM should allow users to specify max disk utilization for local disks

[ https://issues.apache.org/jira/browse/YARN-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1781: Attachment: apache-yarn-1781.1.patch This patch adds support to allows users to specify a minimum

[jira] [Commented] (YARN-1785) FairScheduler treats app lookup failures as ERRORs

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

[jira] [Updated] (YARN-1761) RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby

[ https://issues.apache.org/jira/browse/YARN-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1761: Attachment: YARN-1761.3.patch Submit the same patch again RMAdminCLI should check whether HA is enabled

[jira] [Created] (YARN-1788) AppsCompleted/AppsKilled metric is incorrect when MR job is killed with yarn application -kill

Tassapol Athiapinya created YARN-1788: - Summary: AppsCompleted/AppsKilled metric is incorrect when MR job is killed with yarn application -kill Key: YARN-1788 URL:

[jira] [Commented] (YARN-1781) NM should allow users to specify max disk utilization for local disks

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

[jira] [Commented] (YARN-1761) RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby

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

[jira] [Commented] (YARN-1786) TestRMAppTransitions occasionally fail

[ https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921152#comment-13921152 ] Jian He commented on YARN-1786: --- It seems you have a stale code which is different from the

[jira] [Commented] (YARN-1752) Unexpected Unregistered event at Attempt Launched state

[ https://issues.apache.org/jira/browse/YARN-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921165#comment-13921165 ] Jian He commented on YARN-1752: --- Patch looks good, +1 , thanks Rohith! Unexpected

[jira] [Commented] (YARN-1785) FairScheduler treats app lookup failures as ERRORs

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

[jira] [Commented] (YARN-1752) Unexpected Unregistered event at Attempt Launched state

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

[jira] [Commented] (YARN-1389) ApplicationClientProtocol and ApplicationHistoryProtocol should expose analogous APIs

[ https://issues.apache.org/jira/browse/YARN-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921265#comment-13921265 ] Zhijie Shen commented on YARN-1389: --- 1. In javadoc of ApplicationClientProtocol, we

[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=13921270#comment-13921270 ] Chris Trezzo commented on YARN-1492: Thanks [~kkambatl] for the comments! bq. Would

[jira] [Commented] (YARN-1752) Unexpected Unregistered event at Attempt Launched state

[ https://issues.apache.org/jira/browse/YARN-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921276#comment-13921276 ] Jian He commented on YARN-1752: --- Committed to trunk, branch-2 and branch-2.4, thanks Rohith!

[jira] [Updated] (YARN-1761) RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby

[ https://issues.apache.org/jira/browse/YARN-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1761: Attachment: YARN-1761.4.patch RMAdminCLI should check whether HA is enabled before executes

[jira] [Commented] (YARN-1761) RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby

[ https://issues.apache.org/jira/browse/YARN-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921284#comment-13921284 ] Xuan Gong commented on YARN-1761: - fix -1 on findbug The testcase failure is un-related

[jira] [Updated] (YARN-1640) Manual Failover does not work in secure clusters

[ https://issues.apache.org/jira/browse/YARN-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1640: -- Priority: Blocker (was: Major) Target Version/s: 2.4.0 Seems like

[jira] [Commented] (YARN-1761) RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby

[ https://issues.apache.org/jira/browse/YARN-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921343#comment-13921343 ] Xuan Gong commented on YARN-1761: - Run command: yarn rmadmin -help * With HA {code}

[jira] [Commented] (YARN-1761) RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby

[ https://issues.apache.org/jira/browse/YARN-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921348#comment-13921348 ] Xuan Gong commented on YARN-1761: - Without HA {code} rmadmin is the command to execute YARN

[jira] [Commented] (YARN-1761) RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby

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

[jira] [Commented] (YARN-1761) RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby

[ https://issues.apache.org/jira/browse/YARN-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921397#comment-13921397 ] Vinod Kumar Vavilapalli commented on YARN-1761: --- Okay, looks good. Checking

[jira] [Commented] (YARN-1761) RMAdminCLI should check whether HA is enabled before executes transitionToActive/transitionToStandby

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

[jira] [Resolved] (YARN-1784) TestContainerAllocation assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-1784. Resolution: Won't Fix The test fails locally when run against FairScheduler, but passes on

[jira] [Updated] (YARN-1338) Recover localized resource cache state upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1338: - Attachment: YARN-1338.patch Patch to recover the localized resource cache state when NM recovery is

[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-tabpanelfocusedCommentId=13921516#comment-13921516 ] Cindy Li commented on YARN-1525: @Karthik, Thanks for reviewing it. To respond to your

[jira] [Commented] (YARN-1338) Recover localized resource cache state upon nodemanager restart

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

[jira] [Updated] (YARN-1685) Bugs around log URL

[ https://issues.apache.org/jira/browse/YARN-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1685: -- Target Version/s: 2.4.0 Fix Version/s: (was: YARN-321) Hadoop

[jira] [Updated] (YARN-1787) yarn applicationattempt/container print wrong usage information

[ https://issues.apache.org/jira/browse/YARN-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1787: -- Attachment: YARN-1787.1.patch Fix the usage message and add corresponding test case. After the patch,

[jira] [Commented] (YARN-1410) Handle RM fails over after getApplicationID() and before submitApplication().

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921649#comment-13921649 ] Vinod Kumar Vavilapalli commented on YARN-1410: --- Tx for the clarification.

[jira] [Commented] (YARN-1787) yarn applicationattempt/container print wrong usage information

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

[jira] [Created] (YARN-1789) ApplicationSummary does not escape newlines in the app name

Akira AJISAKA created YARN-1789: --- Summary: ApplicationSummary does not escape newlines in the app name Key: YARN-1789 URL: https://issues.apache.org/jira/browse/YARN-1789 Project: Hadoop YARN

[jira] [Updated] (YARN-1787) yarn applicationattempt/container print wrong usage information

[ https://issues.apache.org/jira/browse/YARN-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1787: - Attachment: ApplicationCLI.java.rej [~zjshen], thank you for taking this JIRA. I tried to patch

[jira] [Commented] (YARN-1787) yarn applicationattempt/container print wrong usage information

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

[jira] [Commented] (YARN-1781) NM should allow users to specify max disk utilization for local disks

[ https://issues.apache.org/jira/browse/YARN-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921804#comment-13921804 ] Xuan Gong commented on YARN-1781: - The patch looks fine to me. One nit: {code} +

[jira] [Updated] (YARN-1787) yarn applicationattempt/container print wrong usage information

[ https://issues.apache.org/jira/browse/YARN-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1787: -- Attachment: YARN-1787.2.patch Upload a new patch, which rebase against the latest trunk yarn

[jira] [Commented] (YARN-1389) ApplicationClientProtocol and ApplicationHistoryProtocol should expose analogous APIs

[ https://issues.apache.org/jira/browse/YARN-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13921878#comment-13921878 ] Zhijie Shen commented on YARN-1389: --- I realize there will be an issue that may not have

[jira] [Commented] (YARN-1787) yarn applicationattempt/container print wrong usage information

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

[jira] [Commented] (YARN-1786) TestRMAppTransitions occasionally fail

[ https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922006#comment-13922006 ] shenhong commented on YARN-1786: Thanks Jian He. The code I used is from

[jira] [Commented] (YARN-1389) ApplicationClientProtocol and ApplicationHistoryProtocol should expose analogous APIs

[ https://issues.apache.org/jira/browse/YARN-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922007#comment-13922007 ] Jian He commented on YARN-1389: --- I think SchedulerApplicationAttempt.liveContainers is

[jira] [Commented] (YARN-1389) ApplicationClientProtocol and ApplicationHistoryProtocol should expose analogous APIs

[ https://issues.apache.org/jira/browse/YARN-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922016#comment-13922016 ] Jian He commented on YARN-1389: --- sorry, my previous message is incorrect. I was in wrong

[jira] [Commented] (YARN-1786) TestRMAppTransitions occasionally fail

[ https://issues.apache.org/jira/browse/YARN-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922025#comment-13922025 ] Jian He commented on YARN-1786: --- The latest trunk shouldn't have such problem because each

[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=13922063#comment-13922063 ] Karthik Kambatla commented on YARN-1492: Thanks [~ctrezzo] for the clarifications.

[jira] [Updated] (YARN-1685) Bugs around log URL

[ https://issues.apache.org/jira/browse/YARN-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1685: -- Attachment: YARN-1685.3.patch Bugs around log URL --- Key:

[jira] [Commented] (YARN-1685) Bugs around log URL

[ https://issues.apache.org/jira/browse/YARN-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922074#comment-13922074 ] Zhijie Shen commented on YARN-1685: --- Vinod, thanks for the review. I've updated the

[jira] [Commented] (YARN-1685) Bugs around log URL

[ https://issues.apache.org/jira/browse/YARN-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922078#comment-13922078 ] Zhijie Shen commented on YARN-1685: --- BTW, it won't lead to race condition, because the

[jira] [Updated] (YARN-1774) FS: Submitting to non-leaf queue throws NPE

[ https://issues.apache.org/jira/browse/YARN-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1774: --- Attachment: yarn-1774-2.patch [~adhoot] is out on vacation. Posting a patch that addresses

[jira] [Updated] (YARN-1790) FairSchedule UI not showing apps table

[ https://issues.apache.org/jira/browse/YARN-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bc Wong updated YARN-1790: -- Attachment: fs_ui.png FairSchedule UI not showing apps table --

[jira] [Commented] (YARN-1774) FS: Submitting to non-leaf queue throws NPE

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