[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-tabpanel&focusedCommentId=13923666#comment-13923666 ] Tsuyoshi OZAWA commented on YARN-1591: -- Hi [~vinodkv], it's failing on trunk on my loc

[jira] [Commented] (YARN-1701) More intuitive defaults for AHS

[ https://issues.apache.org/jira/browse/YARN-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923658#comment-13923658 ] Zhijie Shen commented on YARN-1701: --- bq. I agree the configuration needs to be simple. So

[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-tabpanel&focusedCommentId=13923651#comment-13923651 ] Zhijie Shen commented on YARN-1717: --- Hi Billie, thanks for patch. I've just a quick glanc

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

[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 ] Sangjin Lee updated YARN-1771: -- Attachment: yarn-1771.patch A new patch is uploaded. I found that a test in hadoop-mapreduce-client-comm

[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-tabpanel&focusedCommentId=13923621#comment-13923621 ] Zhijie Shen commented on YARN-1787: --- bq. I am fairly sure you broke bin/yarn appliciation

[jira] [Commented] (YARN-1793) yarn application -kill doesn't kill UnmanagedAMs

[ https://issues.apache.org/jira/browse/YARN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923591#comment-13923591 ] Hadoop QA commented on YARN-1793: - {color:green}+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-tabpanel&focusedCommentId=13923574#comment-13923574 ] Zhijie Shen commented on YARN-1389: --- I've tested the patch locally. "yarn applicationatte

[jira] [Commented] (YARN-1799) Enhance LocalDirAllocator in NM to consider DiskMaxUtilization cutoff

[ https://issues.apache.org/jira/browse/YARN-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923570#comment-13923570 ] Sunil G commented on YARN-1799: --- I would like to take up this JIRA. > Enhance LocalDirAlloca

[jira] [Commented] (YARN-1793) yarn application -kill doesn't kill UnmanagedAMs

[ https://issues.apache.org/jira/browse/YARN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923568#comment-13923568 ] Karthik Kambatla commented on YARN-1793: Thanks for digging up the reason, [~jianhe

[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-tabpanel&focusedCommentId=13923569#comment-13923569 ] Zhijie Shen commented on YARN-1389: --- Thanks for the update, Mayank! The patch is general

[jira] [Commented] (YARN-1764) Handle RM fail overs after the submitApplication call.

[ https://issues.apache.org/jira/browse/YARN-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923566#comment-13923566 ] Vinod Kumar Vavilapalli commented on YARN-1764: --- I think we should also mark

[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=13923565#comment-13923565 ] Hudson commented on YARN-1525: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5280 (See [https:

[jira] [Commented] (YARN-1780) Improve logging in timeline service

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

[jira] [Updated] (YARN-1793) yarn application -kill doesn't kill UnmanagedAMs

[ https://issues.apache.org/jira/browse/YARN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1793: --- Attachment: yarn-1793-1.patch > yarn application -kill doesn't kill UnmanagedAMs > ---

[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-tabpanel&focusedCommentId=13923563#comment-13923563 ] Sunil G commented on YARN-1781: --- I have created a separate JIRA YARN-1799 as per the comment

[jira] [Created] (YARN-1799) Enhance LocalDirAllocator in NM to consider DiskMaxUtilization cutoff

Sunil G created YARN-1799: - Summary: Enhance LocalDirAllocator in NM to consider DiskMaxUtilization cutoff Key: YARN-1799 URL: https://issues.apache.org/jira/browse/YARN-1799 Project: Hadoop YARN Is

[jira] [Commented] (YARN-1795) Oozie tests are flakey after YARN-713

[ https://issues.apache.org/jira/browse/YARN-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923552#comment-13923552 ] Robert Kanter commented on YARN-1795: - Looking at the printouts I added to the NMTokenC

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

[jira] [Commented] (YARN-1798) TestContainerLaunch, TestContainersMonitor, TestNodeManagerShutdown, TestNodeStatusUpdater fails on Linux

[ https://issues.apache.org/jira/browse/YARN-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923546#comment-13923546 ] Tsuyoshi OZAWA commented on YARN-1798: -- Here is a result of test execution locally.

[jira] [Commented] (YARN-1798) TestContainerLaunch, TestContainersMonitor, TestNodeManagerShutdown, TestNodeStatusUpdater fails on Linux

[ https://issues.apache.org/jira/browse/YARN-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923545#comment-13923545 ] Tsuyoshi OZAWA commented on YARN-1798: -- Here is {code} Failed tests:

[jira] [Created] (YARN-1798) TestContainerLaunch, TestContainersMonitor, TestNodeManagerShutdown, TestNodeStatusUpdater fails on Linux

Tsuyoshi OZAWA created YARN-1798: Summary: TestContainerLaunch, TestContainersMonitor, TestNodeManagerShutdown, TestNodeStatusUpdater fails on Linux Key: YARN-1798 URL: https://issues.apache.org/jira/browse/YARN-1

[jira] [Created] (YARN-1797) TestNodeManagerResync,jjjjjjjjjjjjj

Tsuyoshi OZAWA created YARN-1797: Summary: TestNodeManagerResync,j Key: YARN-1797 URL: https://issues.apache.org/jira/browse/YARN-1797 Project: Hadoop YARN Issue Type: Bug

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

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923540#comment-13923540 ] Vinod Kumar Vavilapalli commented on YARN-1621: --- It doesn't look like YARN-13

[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 ] Vinod Kumar Vavilapalli updated YARN-1389: -- Target Version/s: 2.4.0 This is important part of the generic-history feature fo

[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=13923531#comment-13923531 ] Karthik Kambatla commented on YARN-1525: Thanks Cindy. +1 on the latest patch. Comm

[jira] [Updated] (YARN-1795) Oozie tests are flakey after YARN-713

[ https://issues.apache.org/jira/browse/YARN-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-1795: Attachment: syslog org.apache.oozie.action.hadoop.TestMapReduceActionExecutor-output

[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-tabpanel&focusedCommentId=13923521#comment-13923521 ] Vinod Kumar Vavilapalli commented on YARN-1787: --- I am fairly sure you broke b

[jira] [Commented] (YARN-1780) Improve logging in timeline service

[ https://issues.apache.org/jira/browse/YARN-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923507#comment-13923507 ] Vinod Kumar Vavilapalli commented on YARN-1780: --- This looks good, +1. Checkin

[jira] [Commented] (YARN-1793) yarn application -kill doesn't kill UnmanagedAMs

[ https://issues.apache.org/jira/browse/YARN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923491#comment-13923491 ] Jian He commented on YARN-1793: --- Took a quick look at the patch, if I remember correctly, the

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

[jira] [Updated] (YARN-1342) Recover container tokens upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1342: - Attachment: YARN-1342.patch Patch to recover container tokens after a restart. This is very similar to th

[jira] [Commented] (YARN-1795) Oozie tests are flakey after YARN-713

[ https://issues.apache.org/jira/browse/YARN-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923457#comment-13923457 ] Vinod Kumar Vavilapalli commented on YARN-1795: --- Per [~sseth], it is likely t

[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-tabpanel&focusedCommentId=13923434#comment-13923434 ] Vinod Kumar Vavilapalli commented on YARN-1410: --- Okay, I went back and reread

[jira] [Commented] (YARN-1796) container-executor shouldn't require o-r permissions

[ https://issues.apache.org/jira/browse/YARN-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923433#comment-13923433 ] Vinod Kumar Vavilapalli commented on YARN-1796: --- I think I originally did tha

[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=13923406#comment-13923406 ] Cindy Li commented on YARN-1525: That was for another patch... Ok. I should've removed that

[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 ] Karthik Kambatla updated YARN-1525: --- Attachment: YARN1525.secure.v11.patch Thanks Cindy. Posting a patch with cosmetic changes (for

[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=13923398#comment-13923398 ] Cindy Li commented on YARN-1525: The test org.apache.hadoop.yarn.client.api.impl.TestNMClie

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

[jira] [Created] (YARN-1796) container-executor shouldn't require o-r permissions

Aaron T. Myers created YARN-1796: Summary: container-executor shouldn't require o-r permissions Key: YARN-1796 URL: https://issues.apache.org/jira/browse/YARN-1796 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-1796) container-executor shouldn't require o-r permissions

[ https://issues.apache.org/jira/browse/YARN-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers updated YARN-1796: - Attachment: YARN-1796.patch Simple patch attached to relax the mode check in the container-executo

[jira] [Updated] (YARN-1795) Oozie tests are flakey after YARN-713

[ https://issues.apache.org/jira/browse/YARN-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1795: --- Target Version/s: 2.4.0 > Oozie tests are flakey after YARN-713 >

[jira] [Updated] (YARN-1795) Oozie tests are flakey after YARN-713

[ https://issues.apache.org/jira/browse/YARN-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1795: --- Priority: Critical (was: Major) > Oozie tests are flakey after YARN-713 > ---

[jira] [Commented] (YARN-1341) Recover NMTokens upon nodemanager restart

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

[jira] [Created] (YARN-1795) Oozie tests are flakey after YARN-713

Robert Kanter created YARN-1795: --- Summary: Oozie tests are flakey after YARN-713 Key: YARN-1795 URL: https://issues.apache.org/jira/browse/YARN-1795 Project: Hadoop YARN Issue Type: Bug Aff

[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 ] Sangjin Lee updated YARN-1771: -- Attachment: yarn-1771.patch Fixed javadoc. > many getFileStatus calls made from node manager for locali

[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: --- Attachment: YARN1525.secure.v10.patch Made changes according to Karthik's comments. > Web UI should redirect

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

[ https://issues.apache.org/jira/browse/YARN-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923306#comment-13923306 ] Sandy Ryza commented on YARN-1790: -- +1 > FairSchedule UI not showing apps table > ---

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

[ https://issues.apache.org/jira/browse/YARN-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923302#comment-13923302 ] Mayank Bansal commented on YARN-1621: - It should be covered by YARN-1389 Thanks, Mayan

[jira] [Commented] (YARN-1794) Yarn CLI only shows running containers for Running Applications

[ https://issues.apache.org/jira/browse/YARN-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923297#comment-13923297 ] Mayank Bansal commented on YARN-1794: - After YARN-1389 we have capability to show Attem

[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-tabpanel&focusedCommentId=13923301#comment-13923301 ] Mayank Bansal commented on YARN-1389: - Opened the JIRA for this issue YARN-1794 Thanks

[jira] [Updated] (YARN-1794) Yarn CLI only shows running containers for Running Applications

[ https://issues.apache.org/jira/browse/YARN-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-1794: Description: (was: As we plan to have the APIs in ApplicationHistoryProtocol to expose the repor

[jira] [Created] (YARN-1794) Yarn CLI only shows running containers for Running Applications

Mayank Bansal created YARN-1794: --- Summary: Yarn CLI only shows running containers for Running Applications Key: YARN-1794 URL: https://issues.apache.org/jira/browse/YARN-1794 Project: Hadoop YARN

[jira] [Updated] (YARN-1341) Recover NMTokens upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1341: - Attachment: YARN-1341v2.patch Revised patch without the addition of the state store to the NM context sinc

[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-tabpanel&focusedCommentId=13923294#comment-13923294 ] Hadoop QA commented on YARN-1771: - {color:red}-1 overall{color}. Here are the results of t

[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-5.patch Updating latest patch. Thanks, Mayank > ApplicationClientProtocol an

[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-tabpanel&focusedCommentId=13923280#comment-13923280 ] Mayank Bansal commented on YARN-1389: - bq .I realize there will be an issue that may no

[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-tabpanel&focusedCommentId=13923278#comment-13923278 ] Mayank Bansal commented on YARN-1389: - Thanks [~zjshen] for review bq. 1. In javadoc of

[jira] [Commented] (YARN-1341) Recover NMTokens upon nodemanager restart

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

[jira] [Updated] (YARN-1341) Recover NMTokens upon nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1341: - Attachment: YARN-1341.patch Patch to enable the recovery of NMTokens. Like YARN-1338 it uses leveldb as a

[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-tabpanel&focusedCommentId=13923226#comment-13923226 ] Sangjin Lee commented on YARN-1771: --- I have created a status cache at the LocalizerContex

[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 ] Sangjin Lee updated YARN-1771: -- Attachment: yarn-1771.patch > many getFileStatus calls made from node manager for localizing a public >

[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-tabpanel&focusedCommentId=13923176#comment-13923176 ] Sangjin Lee commented on YARN-1771: --- I have been looking into this from the perspective o

[jira] [Updated] (YARN-1793) yarn application -kill doesn't kill UnmanagedAMs

[ https://issues.apache.org/jira/browse/YARN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1793: --- Attachment: yarn-1793-0.patch Simple patch that seems to fix the issue. Removed UnmanagedAM fr

[jira] [Commented] (YARN-1793) yarn application -kill doesn't kill UnmanagedAMs

[ https://issues.apache.org/jira/browse/YARN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923099#comment-13923099 ] Karthik Kambatla commented on YARN-1793: What do you think about getting rid of thi

[jira] [Commented] (YARN-1783) yarn application does not make any progress even when no other application is running when RM is being restarted in the background

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

[jira] [Assigned] (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 ] Xuan Gong reassigned YARN-1619: --- Assignee: Xuan Gong > Add cli to kill yarn container > -- > >

[jira] [Resolved] (YARN-1792) Add a CLI to kill yarn container

[ https://issues.apache.org/jira/browse/YARN-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli resolved YARN-1792. --- Resolution: Duplicate Closing as duplicate. > Add a CLI to kill yarn containe

[jira] [Commented] (YARN-1793) yarn application -kill doesn't kill UnmanagedAMs

[ https://issues.apache.org/jira/browse/YARN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923050#comment-13923050 ] Jian He commented on YARN-1793: --- Thanks for finding this issue. UnmanagedAM is not going thro

[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=13923039#comment-13923039 ] Karthik Kambatla commented on YARN-1525: bq. In the case the standby RM, where isSt

[jira] [Commented] (YARN-1783) yarn application does not make any progress even when no other application is running when RM is being restarted in the background

[ https://issues.apache.org/jira/browse/YARN-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923038#comment-13923038 ] Xuan Gong commented on YARN-1783: - +1 LGTM > yarn application does not make any progress e

[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.4.patch Upload a new patch: 1. Move the logic of constructing the log URL pointin

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

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

[jira] [Commented] (YARN-1793) yarn application -kill doesn't kill UnmanagedAMs

[ https://issues.apache.org/jira/browse/YARN-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922989#comment-13922989 ] Karthik Kambatla commented on YARN-1793: {code} if (application.isAppSafeToTerm

[jira] [Created] (YARN-1793) yarn application -kill doesn't kill UnmanagedAMs

Karthik Kambatla created YARN-1793: -- Summary: yarn application -kill doesn't kill UnmanagedAMs Key: YARN-1793 URL: https://issues.apache.org/jira/browse/YARN-1793 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-1792) Add a CLI to kill yarn container

[ https://issues.apache.org/jira/browse/YARN-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922970#comment-13922970 ] Ramya Sunil commented on YARN-1792: --- Duplicate of YARN-1619 > Add a CLI to kill yarn con

[jira] [Updated] (YARN-1792) Add a CLI to kill yarn container

[ https://issues.apache.org/jira/browse/YARN-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tassapol Athiapinya updated YARN-1792: -- Description: One of my teammates saw an issue when there was dangling container. The rea

[jira] [Assigned] (YARN-1792) Add a CLI to kill yarn container

[ https://issues.apache.org/jira/browse/YARN-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-1792: --- Assignee: Xuan Gong > Add a CLI to kill yarn container > > >

[jira] [Updated] (YARN-1783) yarn application does not make any progress even when no other application is running when RM is being restarted in the background

[ https://issues.apache.org/jira/browse/YARN-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1783: -- Attachment: YARN-1783.3.patch Thanks for catching this ! The new patch creates a separate collection for recordi

[jira] [Created] (YARN-1792) Add a CLI to kill yarn container

Tassapol Athiapinya created YARN-1792: - Summary: Add a CLI to kill yarn container Key: YARN-1792 URL: https://issues.apache.org/jira/browse/YARN-1792 Project: Hadoop YARN Issue Type: Impr

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

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

[jira] [Resolved] (YARN-1467) implement checksum verification for resource localization service for the shared cache

[ https://issues.apache.org/jira/browse/YARN-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee resolved YARN-1467. --- Resolution: Invalid I'll close out these JIRAs for YARN-1492, as the design has changed from the time

[jira] [Resolved] (YARN-1466) implement the cleaner service for the shared cache

[ https://issues.apache.org/jira/browse/YARN-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee resolved YARN-1466. --- Resolution: Invalid I'll close out these JIRAs for YARN-1492, as the design has changed from the time

[jira] [Resolved] (YARN-1465) define and add shared constants and utilities for the shared cache

[ https://issues.apache.org/jira/browse/YARN-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee resolved YARN-1465. --- Resolution: Invalid I'll close out these JIRAs for YARN-1492, as the design has changed from the time

[jira] [Commented] (YARN-1783) yarn application does not make any progress even when no other application is running when RM is being restarted in the background

[ https://issues.apache.org/jira/browse/YARN-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922920#comment-13922920 ] Xuan Gong commented on YARN-1783: - The logic to handle NodeAction.RESYNC looks good to me.

[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-tabpanel&focusedCommentId=13922906#comment-13922906 ] Chris Trezzo commented on YARN-1492: bq. Do you want to go ahead and create sub-tasks?

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

[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: 0001-YARN-1790.-FairScheduler-UI-not-showing-apps-table.patch Same patch with --no-prefix. > FairSc

[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: (was: 0001-YARN-1790.-FairScheduler-UI-not-showing-apps-table.patch) > FairSchedule UI not show

[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-tabpanel&focusedCommentId=13922832#comment-13922832 ] Xuan Gong commented on YARN-1410: - create a new patch to address all the comments, which in

[jira] [Updated] (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:all-tabpanel ] Xuan Gong updated YARN-1410: Attachment: YARN-1410.10.patch > Handle RM fails over after getApplicationID() and before submitApplication(

[jira] [Updated] (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:all-tabpanel ] Xuan Gong updated YARN-1410: Attachment: YARN-1410.10.patch > Handle RM fails over after getApplicationID() and before submitApplication(

[jira] [Commented] (YARN-1791) Distributed cache issue using YARN

[ https://issues.apache.org/jira/browse/YARN-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922651#comment-13922651 ] Ashish Kumar commented on YARN-1791: Thank you Jason! I'll use that email for any furth

[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-tabpanel&focusedCommentId=13922590#comment-13922590 ] Hudson commented on YARN-1761: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1718 (See [htt

[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-tabpanel&focusedCommentId=13922596#comment-13922596 ] Hudson commented on YARN-1785: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1718 (See [htt

[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-tabpanel&focusedCommentId=13922589#comment-13922589 ] Hudson commented on YARN-1752: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1718 (See [htt

[jira] [Resolved] (YARN-1791) Distributed cache issue using YARN

[ https://issues.apache.org/jira/browse/YARN-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-1791. -- Resolution: Invalid The distributed cache only preserves the basename of files and links them into the

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

[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-tabpanel&focusedCommentId=13922406#comment-13922406 ] Hudson commented on YARN-1785: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #501 (See [https://b

[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-tabpanel&focusedCommentId=13922399#comment-13922399 ] Hudson commented on YARN-1752: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #501 (See [https://b

  1   2   >