[jira] [Commented] (YARN-1591) TestResourceTrackerService fails randomly on trunk

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

[jira] [Updated] (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:all-tabpanel ] Varun Vasudev updated YARN-90: -- Attachment: apache-yarn-90.2.patch Fixed issue that caused the patch application to fail. NodeManager

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

[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=13932950#comment-13932950 ] Zhijie Shen commented on YARN-1389: --- Test failures are not related.

[jira] [Commented] (YARN-1577) Unmanaged AM is broken because of YARN-1493

[ https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13932957#comment-13932957 ] Zhijie Shen commented on YARN-1577: --- Hi, Naren. YARN-1389 is resolved you can make use of

[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=13932960#comment-13932960 ] Hudson commented on YARN-1389: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5316 (See

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

[jira] [Updated] (YARN-1705) Cluster metrics are off after failover

[ https://issues.apache.org/jira/browse/YARN-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1705: - Attachment: YARN-1705.1.patch Hi, I attached patch that handles 1. transtion

[jira] [Created] (YARN-1829) CapacityScheduler can't schedule job after misconfiguration

PengZhang created YARN-1829: --- Summary: CapacityScheduler can't schedule job after misconfiguration Key: YARN-1829 URL: https://issues.apache.org/jira/browse/YARN-1829 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-1829) CapacityScheduler can't schedule job after misconfiguration

[ https://issues.apache.org/jira/browse/YARN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PengZhang updated YARN-1829: Description: CapacityScheduler will validate new configuration to make sure all existing queues are still

[jira] [Updated] (YARN-1829) CapacityScheduler can't schedule job after misconfiguration

[ https://issues.apache.org/jira/browse/YARN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PengZhang updated YARN-1829: Description: CapacityScheduler will validate new configuration to make sure all existing queues are still

[jira] [Updated] (YARN-1829) CapacityScheduler can't schedule job after misconfiguration

[ https://issues.apache.org/jira/browse/YARN-1829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PengZhang updated YARN-1829: Description: CapacityScheduler will validate new configuration to make sure all existing queues are still

[jira] [Commented] (YARN-1824) Make Windows client work with Linux/Unix cluster

[ https://issues.apache.org/jira/browse/YARN-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933059#comment-13933059 ] Steve Loughran commented on YARN-1824: -- My main point was : client code should not

[jira] [Commented] (YARN-1542) Add unit test for public resource on viewfs

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

[jira] [Commented] (YARN-1812) Job stays in PREP state for long time after RM Restarts

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

[jira] [Commented] (YARN-1816) Succeeded application remains in accepted after RM restart

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

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

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

[jira] [Commented] (YARN-1444) RM crashes when node resource request sent without corresponding off-switch request

[ https://issues.apache.org/jira/browse/YARN-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933102#comment-13933102 ] Hudson commented on YARN-1444: -- FAILURE: Integrated in Hadoop-Yarn-trunk #508 (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=13933111#comment-13933111 ] Hudson commented on YARN-1389: -- FAILURE: Integrated in Hadoop-Yarn-trunk #508 (See

[jira] [Commented] (YARN-1816) Succeeded application remains in accepted after RM restart

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

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

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

[jira] [Commented] (YARN-1812) Job stays in PREP state for long time after RM Restarts

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

[jira] [Commented] (YARN-1444) RM crashes when node resource request sent without corresponding off-switch request

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

[jira] [Updated] (YARN-1591) TestResourceTrackerService fails randomly on trunk

[ https://issues.apache.org/jira/browse/YARN-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1591: - Attachment: YARN-1591.3.patch Fixed not to throw YarnRuntimeException when InterruptedException

[jira] [Commented] (YARN-1444) RM crashes when node resource request sent without corresponding off-switch request

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

[jira] [Commented] (YARN-1816) Succeeded application remains in accepted after RM restart

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

[jira] [Commented] (YARN-1591) TestResourceTrackerService fails randomly on trunk

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

[jira] [Commented] (YARN-1812) Job stays in PREP state for long time after RM Restarts

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

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

[ https://issues.apache.org/jira/browse/YARN-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933342#comment-13933342 ] Hudson commented on YARN-1789: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1725 (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=13933350#comment-13933350 ] Hudson commented on YARN-1389: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1725 (See

[jira] [Updated] (YARN-1512) Enhance CS to decouple scheduling from node heartbeats

[ https://issues.apache.org/jira/browse/YARN-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1512: Attachment: YARN-1512.patch Updated, ready I believe. Enhance CS to decouple scheduling from node

[jira] [Commented] (YARN-1512) Enhance CS to decouple scheduling from node heartbeats

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

[jira] [Commented] (YARN-1769) CapacityScheduler: Improve reservations

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933478#comment-13933478 ] Jonathan Eagles commented on YARN-1769: --- Hi, Tom. Can you comment on the findbugs

[jira] [Commented] (YARN-1577) Unmanaged AM is broken because of YARN-1493

[ https://issues.apache.org/jira/browse/YARN-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933541#comment-13933541 ] Naren Koneru commented on YARN-1577: Hi Zhijie, Nice, thanks for letting me know. I

[jira] [Created] (YARN-1830) TestRMRestart.testQueueMetricsOnRMRestart failure

Karthik Kambatla created YARN-1830: -- Summary: TestRMRestart.testQueueMetricsOnRMRestart failure Key: YARN-1830 URL: https://issues.apache.org/jira/browse/YARN-1830 Project: Hadoop YARN

[jira] [Commented] (YARN-1815) RM should recover only Managed AMs

[ https://issues.apache.org/jira/browse/YARN-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933580#comment-13933580 ] Karthik Kambatla commented on YARN-1815: The tests pass locally. Filed YARN-1830

[jira] [Updated] (YARN-1591) TestResourceTrackerService fails randomly on trunk

[ https://issues.apache.org/jira/browse/YARN-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-1591: Assignee: Tsuyoshi OZAWA (was: Vinod Kumar Vavilapalli) TestResourceTrackerService fails randomly

[jira] [Commented] (YARN-1830) TestRMRestart.testQueueMetricsOnRMRestart failure

[ https://issues.apache.org/jira/browse/YARN-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933586#comment-13933586 ] Zhijie Shen commented on YARN-1830: --- See the same failure reported on YARN-1389

[jira] [Commented] (YARN-1512) Enhance CS to decouple scheduling from node heartbeats

[ https://issues.apache.org/jira/browse/YARN-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933582#comment-13933582 ] Arun C Murthy commented on YARN-1512: - Looks like YARN-1591 tracks the failure with

[jira] [Updated] (YARN-1795) After YARN-713, using FairScheduler can cause an InvalidToken Exception for NMTokens

[ https://issues.apache.org/jira/browse/YARN-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-1795: Description: Running the Oozie unit tests against a Hadoop build with YARN-713 causes many of the

[jira] [Updated] (YARN-1795) After YARN-713, using FairScheduler can cause an InvalidToken Exception for NMTokens

[ https://issues.apache.org/jira/browse/YARN-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1795: --- Priority: Blocker (was: Critical) After YARN-713, using FairScheduler can cause an

[jira] [Commented] (YARN-1811) RM HA: AM link broken if the AM is on nodes other than RM

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

[jira] [Commented] (YARN-1815) RM should recover only Managed AMs

[ https://issues.apache.org/jira/browse/YARN-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933639#comment-13933639 ] Jian He commented on YARN-1815: --- Thanks Karthik for the patch. For now, it should be fine to

[jira] [Commented] (YARN-1591) TestResourceTrackerService fails randomly on trunk

[ https://issues.apache.org/jira/browse/YARN-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933820#comment-13933820 ] Tsuyoshi OZAWA commented on YARN-1591: -- test failures looks not related. [~jianhe],

[jira] [Commented] (YARN-1811) RM HA: AM link broken if the AM is on nodes other than RM

[ https://issues.apache.org/jira/browse/YARN-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933825#comment-13933825 ] Robert Kanter commented on YARN-1811: - TestResourceTrackerService is flakey (and fails

[jira] [Commented] (YARN-1769) CapacityScheduler: Improve reservations

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933831#comment-13933831 ] Thomas Graves commented on YARN-1769: - The findbugs can be ignored. They are talking

[jira] [Created] (YARN-1831) Job should be marked as Falied if it is recovered from commit.

Yesha Vora created YARN-1831: Summary: Job should be marked as Falied if it is recovered from commit. Key: YARN-1831 URL: https://issues.apache.org/jira/browse/YARN-1831 Project: Hadoop YARN

[jira] [Updated] (YARN-1769) CapacityScheduler: Improve reservations

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-1769: Attachment: YARN-1769.patch exclude findbugs warnings. CapacityScheduler: Improve reservations

[jira] [Commented] (YARN-1769) CapacityScheduler: Improve reservations

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

[jira] [Assigned] (YARN-1831) Job should be marked as Falied if it is recovered from commit.

[ https://issues.apache.org/jira/browse/YARN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-1831: --- Assignee: Xuan Gong Job should be marked as Falied if it is recovered from commit.

[jira] [Commented] (YARN-1831) Job should be marked as Falied if it is recovered from commit.

[ https://issues.apache.org/jira/browse/YARN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933869#comment-13933869 ] Xuan Gong commented on YARN-1831: - Close this as duplicate Job should be marked as Falied

[jira] [Updated] (YARN-1831) Job should be marked as Falied if it is recovered from commit.

[ https://issues.apache.org/jira/browse/YARN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yesha Vora updated YARN-1831: - Description: If Resource manager is restarted when a job is in commit state, The job is not able to be

[jira] [Commented] (YARN-1811) RM HA: AM link broken if the AM is on nodes other than RM

[ https://issues.apache.org/jira/browse/YARN-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933866#comment-13933866 ] Karthik Kambatla commented on YARN-1811: Thanks Robert. Comments: #

[jira] [Commented] (YARN-1831) Job should be marked as Falied if it is recovered from commit.

[ https://issues.apache.org/jira/browse/YARN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933867#comment-13933867 ] Xuan Gong commented on YARN-1831: - create a MapReduce ticket. Let us start from there:

[jira] [Resolved] (YARN-1831) Job should be marked as Falied if it is recovered from commit.

[ https://issues.apache.org/jira/browse/YARN-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong resolved YARN-1831. - Resolution: Duplicate Job should be marked as Falied if it is recovered from commit.

[jira] [Commented] (YARN-1811) RM HA: AM link broken if the AM is on nodes other than RM

[ https://issues.apache.org/jira/browse/YARN-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933873#comment-13933873 ] Robert Kanter commented on YARN-1811: - I'll make those changes and put up a new patch.

[jira] [Updated] (YARN-1769) CapacityScheduler: Improve reservations

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-1769: Attachment: YARN-1769.patch upmerge patch to latest. CapacityScheduler: Improve reservations

[jira] [Commented] (YARN-1815) RM should recover only Managed AMs

[ https://issues.apache.org/jira/browse/YARN-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933938#comment-13933938 ] Jian He commented on YARN-1815: --- bq. it should be fine to move UMA to Failed state as UMA is

[jira] [Commented] (YARN-1769) CapacityScheduler: Improve reservations

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

[jira] [Commented] (YARN-1591) TestResourceTrackerService fails randomly on trunk

[ https://issues.apache.org/jira/browse/YARN-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934005#comment-13934005 ] Jian He commented on YARN-1591: --- In the scope of this jira, the reason

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934027#comment-13934027 ] Zhijie Shen commented on YARN-1809: --- AHS web-UI is still not able to show tags due to

[jira] [Updated] (YARN-1811) RM HA: AM link broken if the AM is on nodes other than RM

[ https://issues.apache.org/jira/browse/YARN-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-1811: Attachment: YARN-1811.patch New patch addresses Karthik's comments. RM HA: AM link broken if the

[jira] [Resolved] (YARN-1822) Revisit AM link being broken for work preserving restart

[ https://issues.apache.org/jira/browse/YARN-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter resolved YARN-1822. - Resolution: Invalid YARN-1811 is being done differently, and this is no longer needed Revisit

[jira] [Updated] (YARN-1591) TestResourceTrackerService fails randomly on trunk

[ https://issues.apache.org/jira/browse/YARN-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1591: - Attachment: YARN-1591.5.patch [~jianhe] oops, I've overlooked rm is defined locally in the test

[jira] [Updated] (YARN-1717) Enable offline deletion of entries in leveldb timeline store

[ https://issues.apache.org/jira/browse/YARN-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billie Rinaldi updated YARN-1717: - Attachment: YARN-1717.10.patch [~zjshen], thanks for the review. I have implemented your

[jira] [Assigned] (YARN-1536) Cleanup: Get rid of ResourceManager#get*SecretManager() methods and use the RMContext methods instead

[ https://issues.apache.org/jira/browse/YARN-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-1536: --- Assignee: Anubhav Dhoot (was: Karthik Kambatla) Cleanup: Get rid of

[jira] [Updated] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1809: -- Attachment: YARN-1809.2.patch Upload a new patch with the following changes: 1. Rebase against

[jira] [Commented] (YARN-1811) RM HA: AM link broken if the AM is on nodes other than RM

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

[jira] [Commented] (YARN-808) ApplicationReport does not clearly tell that the attempt is running or not

[ https://issues.apache.org/jira/browse/YARN-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934165#comment-13934165 ] Zhijie Shen commented on YARN-808: -- After YARN-1389, we have separate APIs to get the

[jira] [Commented] (YARN-1717) Enable offline deletion of entries in leveldb timeline store

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

[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=13934174#comment-13934174 ] Arun C Murthy commented on YARN-796: Back to this, some thoughts: * Admin interface **

[jira] [Commented] (YARN-1591) TestResourceTrackerService fails randomly on trunk

[ https://issues.apache.org/jira/browse/YARN-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934176#comment-13934176 ] Jian He commented on YARN-1591: --- Thanks for the patch [~ozawa] ! Patch looks good, +1

[jira] [Comment Edited] (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=13934174#comment-13934174 ] Arun C Murthy edited comment on YARN-796 at 3/13/14 10:00 PM: --

[jira] [Commented] (YARN-1811) RM HA: AM link broken if the AM is on nodes other than RM

[ https://issues.apache.org/jira/browse/YARN-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934182#comment-13934182 ] Karthik Kambatla commented on YARN-1811: Changes look good to me. I ll defer the

[jira] [Commented] (YARN-1811) RM HA: AM link broken if the AM is on nodes other than RM

[ https://issues.apache.org/jira/browse/YARN-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934181#comment-13934181 ] Robert Kanter commented on YARN-1811: - Both failures look untreated and already have

[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=13934189#comment-13934189 ] Sandy Ryza commented on YARN-796: - Makes a lot of sense to me. One nit: bq. Each scheduler

[jira] [Commented] (YARN-1591) TestResourceTrackerService fails randomly on trunk

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

[jira] [Updated] (YARN-1536) Cleanup: Get rid of ResourceManager#get*SecretManager() methods and use the RMContext methods instead

[ https://issues.apache.org/jira/browse/YARN-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1536: Attachment: yarn-1536.patch Cleanup: Get rid of ResourceManager#get*SecretManager() methods and

[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=13934246#comment-13934246 ] Arun C Murthy commented on YARN-796: [~sandyr] - Sorry, if it wasn't clear. I meant the

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

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

[jira] [Commented] (YARN-1591) TestResourceTrackerService fails randomly on trunk

[ https://issues.apache.org/jira/browse/YARN-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934245#comment-13934245 ] Tsuyoshi OZAWA commented on YARN-1591: -- [~jianhe], what do you think about the

[jira] [Updated] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1809: -- Attachment: YARN-1809.3.patch Fix the findbugs Synchronize RM and Generic History Service Web-UIs

[jira] [Commented] (YARN-1717) Enable offline deletion of entries in leveldb timeline store

[ https://issues.apache.org/jira/browse/YARN-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934288#comment-13934288 ] Zhijie Shen commented on YARN-1717: --- Some minor things on the patch: 1. Rename the class

[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=13934293#comment-13934293 ] Alejandro Abdelnur commented on YARN-796: - Arun, doing a recap on the config, is

[jira] [Commented] (YARN-1591) TestResourceTrackerService fails randomly on trunk

[ https://issues.apache.org/jira/browse/YARN-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934304#comment-13934304 ] Jian He commented on YARN-1591: --- Seems one more issue here... somehow the

[jira] [Commented] (YARN-1824) Make Windows client work with Linux/Unix cluster

[ https://issues.apache.org/jira/browse/YARN-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934330#comment-13934330 ] Vinod Kumar Vavilapalli commented on YARN-1824: --- Also call

[jira] [Updated] (YARN-1771) many getFileStatus calls made from node manager for localizing a public distributed cache resource

[ https://issues.apache.org/jira/browse/YARN-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Douglas updated YARN-1771: Issue Type: Improvement (was: Bug) many getFileStatus calls made from node manager for localizing

[jira] [Updated] (YARN-1658) Webservice should redirect to active RM when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cindy Li updated YARN-1658: --- Attachment: YARN1658.2.patch Thanks Vinod for the comment. I've changed it to reduce overriding to only to

[jira] [Updated] (YARN-1658) Webservice should redirect to active RM when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cindy Li updated YARN-1658: --- Attachment: YARN1658.3.patch Webservice should redirect to active RM when HA is enabled.

[jira] [Commented] (YARN-1536) Cleanup: Get rid of ResourceManager#get*SecretManager() methods and use the RMContext methods instead

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

[jira] [Commented] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

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

[jira] [Updated] (YARN-1591) TestResourceTrackerService fails randomly on trunk

[ https://issues.apache.org/jira/browse/YARN-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1591: - Attachment: YARN-1591.6.patch This patch works well on local. TestResourceTrackerService fails

[jira] [Commented] (YARN-1771) many getFileStatus calls made from node manager for localizing a public distributed cache resource

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

[jira] [Commented] (YARN-1771) many getFileStatus calls made from node manager for localizing a public distributed cache resource

[ https://issues.apache.org/jira/browse/YARN-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934426#comment-13934426 ] Sangjin Lee commented on YARN-1771: --- Thanks Chris! It would be great if you could commit

[jira] [Commented] (YARN-1591) TestResourceTrackerService fails randomly on trunk

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

[jira] [Commented] (YARN-1658) Webservice should redirect to active RM when HA is enabled.

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

[jira] [Commented] (YARN-1591) TestResourceTrackerService fails randomly on trunk

[ https://issues.apache.org/jira/browse/YARN-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934482#comment-13934482 ] Tsuyoshi OZAWA commented on YARN-1591: -- Fixed not to throw YarnRuntimeException when

[jira] [Commented] (YARN-1658) Webservice should redirect to active RM when HA is enabled.

[ https://issues.apache.org/jira/browse/YARN-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13934487#comment-13934487 ] Vinod Kumar Vavilapalli commented on YARN-1658: --- Both failures are existing

[jira] [Commented] (YARN-1658) Webservice should redirect to active RM when HA is enabled.

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

[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=13934522#comment-13934522 ] Junping Du commented on YARN-796: - bq. ResourceManager yarn-site.xml would specify the valid

  1   2   >