[jira] [Commented] (YARN-1678) Fair scheduler gabs incessantly about reservations

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

[jira] [Commented] (YARN-1686) NodeManager.resyncWithRM() does not handle exception which cause NodeManger to Hang.

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

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

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

[jira] [Commented] (YARN-1686) NodeManager.resyncWithRM() does not handle exception which cause NodeManger to Hang.

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

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

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

[jira] [Commented] (YARN-1678) Fair scheduler gabs incessantly about reservations

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

[jira] [Commented] (YARN-1678) Fair scheduler gabs incessantly about reservations

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

[jira] [Commented] (YARN-1686) NodeManager.resyncWithRM() does not handle exception which cause NodeManger to Hang.

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

[jira] [Commented] (YARN-1734) RM should get the updated Configurations when it transits from Standby to Active

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

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

[ https://issues.apache.org/jira/browse/YARN-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billie Rinaldi updated YARN-1730: - Attachment: YARN-1730.3.patch Rebased patch 1 against trunk. Leveldb timeline store needs

[jira] [Updated] (YARN-1757) Auxiliary service support for nodemanager recovery

[ https://issues.apache.org/jira/browse/YARN-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1757: - Attachment: YARN-1757.patch Patch to have the nodemanager create an aux-service-specific path under the

[jira] [Updated] (YARN-1757) Auxiliary service support for nodemanager recovery

[ https://issues.apache.org/jira/browse/YARN-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1757: - Target Version/s: 2.5.0 (was: 2.4.0) Auxiliary service support for nodemanager recovery

[jira] [Commented] (YARN-1760) TestRMAdminService assumes the use of CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911797#comment-13911797 ] Sandy Ryza commented on YARN-1760: -- +1 TestRMAdminService assumes the use of

[jira] [Updated] (YARN-1760) TestRMAdminService assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1760: --- Summary: TestRMAdminService assumes CapacityScheduler (was: TestRMAdminService assumes the

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

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911817#comment-13911817 ] Xuan Gong commented on YARN-1410: - Sounds good to me. For 1) RM fails over after

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

[jira] [Commented] (YARN-1758) MiniYARNCluster broken post YARN-1666

[ https://issues.apache.org/jira/browse/YARN-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911827#comment-13911827 ] Tsuyoshi OZAWA commented on YARN-1758: -- Thank you for reporting, [~hitesh]. I cannot

[jira] [Commented] (YARN-1760) TestRMAdminService assumes CapacityScheduler

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

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

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911842#comment-13911842 ] Bikas Saha commented on YARN-1410: -- bq. getApplicationReport() is called, we will get an

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

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911845#comment-13911845 ] Karthik Kambatla commented on YARN-1410: As Vinod suggested, can we limit this JIRA

[jira] [Commented] (YARN-1758) MiniYARNCluster broken post YARN-1666

[ https://issues.apache.org/jira/browse/YARN-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911863#comment-13911863 ] Hitesh Shah commented on YARN-1758: --- [~ozawa] The problem is due to the loading of

[jira] [Commented] (YARN-1757) Auxiliary service support for nodemanager recovery

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

[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=13911876#comment-13911876 ] Naren Koneru commented on YARN-1577: Hi Jian, are you working on this issue? If not, I

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

Xuan Gong created YARN-1764: --- Summary: Handle RM fail overs after the submitApplication call. Key: YARN-1764 URL: https://issues.apache.org/jira/browse/YARN-1764 Project: Hadoop YARN Issue Type:

[jira] [Assigned] (YARN-1758) MiniYARNCluster broken post YARN-1666

[ https://issues.apache.org/jira/browse/YARN-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-1758: --- Assignee: Xuan Gong MiniYARNCluster broken post YARN-1666 -

[jira] [Updated] (YARN-1713) Implement getnewapplication as part of RM web service

[ https://issues.apache.org/jira/browse/YARN-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1713: Attachment: (was: yarn-1713.patch) Implement getnewapplication as part of RM web service

[jira] [Updated] (YARN-1713) Implement getnewapplication as part of RM web service

[ https://issues.apache.org/jira/browse/YARN-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1713: Attachment: apache-yarn-1713.patch Implement getnewapplication as part of RM web service

[jira] [Commented] (YARN-1758) MiniYARNCluster broken post YARN-1666

[ https://issues.apache.org/jira/browse/YARN-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911902#comment-13911902 ] Xuan Gong commented on YARN-1758: - Do not move the configs out of

[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=13911903#comment-13911903 ] Jian He commented on YARN-1577: --- Hi [~naren.koneru], sure, you can work on it. Tx Unmanaged

[jira] [Commented] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

[ https://issues.apache.org/jira/browse/YARN-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911910#comment-13911910 ] Varun Vasudev commented on YARN-1713: - Attached two patch files. Testing for the

[jira] [Updated] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

[ https://issues.apache.org/jira/browse/YARN-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-1713: Summary: Implement getnewapplication and submitapp as part of RM web service (was: Implement

[jira] [Assigned] (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:all-tabpanel ] Naren Koneru reassigned YARN-1577: -- Assignee: Naren Koneru (was: Jian He) Unmanaged AM is broken because of YARN-1493

[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=13911947#comment-13911947 ] Zhijie Shen commented on YARN-1730: --- bq. The hold count only returns the number of holds

[jira] [Commented] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

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

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

[ https://issues.apache.org/jira/browse/YARN-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billie Rinaldi updated YARN-1730: - Attachment: YARN-1730.4.patch Sounds fine to me. Leveldb timeline store needs simple write

[jira] [Updated] (YARN-1757) Auxiliary service support for nodemanager recovery

[ https://issues.apache.org/jira/browse/YARN-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-1757: - Attachment: YARN-1757.patch Test failures are of the Bind address already in use variety, and the NM

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

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13912071#comment-13912071 ] Xuan Gong commented on YARN-1410: - Create https://issues.apache.org/jira/browse/YARN-1763

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

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

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

[jira] [Commented] (YARN-1757) Auxiliary service support for nodemanager recovery

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

[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=13912144#comment-13912144 ] Karthik Kambatla commented on YARN-1492: Thanks for sharing this, [~ctrezzo]. The

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

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

[jira] [Updated] (YARN-1740) Redirection from AM-URL is broken with HTTPS_ONLY policy

[ https://issues.apache.org/jira/browse/YARN-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1740: -- Attachment: YARN-1740.2.patch Redirection from AM-URL is broken with HTTPS_ONLY policy

[jira] [Commented] (YARN-1740) Redirection from AM-URL is broken with HTTPS_ONLY policy

[ https://issues.apache.org/jira/browse/YARN-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13912176#comment-13912176 ] Jian He commented on YARN-1740: --- Added a test case for testing MR web app is explicitly

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

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

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

[ https://issues.apache.org/jira/browse/YARN-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13912188#comment-13912188 ] Xuan Gong commented on YARN-1410: - Test case is passing locally. Added verifyConnections()

[jira] [Updated] (YARN-1729) ATSWebServices always passes primary and secondary filters as strings

[ https://issues.apache.org/jira/browse/YARN-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billie Rinaldi updated YARN-1729: - Attachment: YARN-1729.3.patch Updated patch for trunk. ATSWebServices always passes primary and

[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.patch Initial patch, based on YARN1525 patch. Webservice should redirect to active RM

[jira] [Commented] (YARN-1740) Redirection from AM-URL is broken with HTTPS_ONLY policy

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

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

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

[jira] [Commented] (YARN-1700) AHS records non-launched containers

[ https://issues.apache.org/jira/browse/YARN-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13912383#comment-13912383 ] Zhijie Shen commented on YARN-1700: --- Log url is nullable. In this scenario, the container

[jira] [Commented] (YARN-1729) ATSWebServices always passes primary and secondary filters as strings

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

[jira] [Commented] (YARN-1713) Implement getnewapplication and submitapp as part of RM web service

[ https://issues.apache.org/jira/browse/YARN-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13912394#comment-13912394 ] Jian He commented on YARN-1713: --- Some comments on patch apache-yarn-1713.cumulative.patch: -

[jira] [Updated] (YARN-1588) Rebind NM tokens for previous attempt's running containers to the new attempt

[ https://issues.apache.org/jira/browse/YARN-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-1588: -- Attachment: YARN-1588.5.patch Refactored some logging in the new patch Rebind NM tokens for previous

[jira] [Updated] (YARN-1429) YARN_CLASSPATH is referenced in yarn command comments but doesn't do anything

[ https://issues.apache.org/jira/browse/YARN-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated YARN-1429: - Attachment: YARN-1429.patch Attaching updated version that changed the name to

[jira] [Commented] (YARN-1588) Rebind NM tokens for previous attempt's running containers to the new attempt

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

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

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

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

[jira] [Updated] (YARN-1429) YARN_CLASSPATH is referenced in yarn command comments but doesn't do anything

[ https://issues.apache.org/jira/browse/YARN-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated YARN-1429: - Attachment: YARN-1429.linux.patch I've noticed that my generated patch can't be easily

[jira] [Updated] (YARN-1363) Get / Cancel / Renew delegation token api should be non blocking

[ https://issues.apache.org/jira/browse/YARN-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1363: -- Hadoop Flags: Incompatible change Get / Cancel / Renew delegation token api should be non blocking

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

[ https://issues.apache.org/jira/browse/YARN-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-1752: Assignee: Rohith Unexpected Unregistered event at Attempt Launched state

[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=13912501#comment-13912501 ] Rohith commented on YARN-1752: -- I reproduced this case using debug point. This need to be

[jira] [Commented] (YARN-1588) Rebind NM tokens for previous attempt's running containers to the new attempt

[ https://issues.apache.org/jira/browse/YARN-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13912516#comment-13912516 ] Jian He commented on YARN-1588: --- Can't reproduce test failure locally, it can be similar to

[jira] [Commented] (YARN-1700) AHS records non-launched containers

[ https://issues.apache.org/jira/browse/YARN-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13912515#comment-13912515 ] Gera Shegalov commented on YARN-1700: - Log URL is physically nullable, but in the

[jira] [Commented] (YARN-1429) YARN_CLASSPATH is referenced in yarn command comments but doesn't do anything

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

[jira] [Resolved] (YARN-1700) AHS records non-launched containers

[ https://issues.apache.org/jira/browse/YARN-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-1700. --- Resolution: Duplicate AHS records non-launched containers ---

[jira] [Commented] (YARN-1700) AHS records non-launched containers

[ https://issues.apache.org/jira/browse/YARN-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13912551#comment-13912551 ] Zhijie Shen commented on YARN-1700: --- bq. Log URL is physically nullable, but in the

[jira] [Updated] (YARN-1685) Log URL should be different when the container is running and finished, and null case needs to be handled

[ https://issues.apache.org/jira/browse/YARN-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1685: -- Summary: Log URL should be different when the container is running and finished, and null case needs to

[jira] [Created] (YARN-1765) Write test cases to verify that killApplication API works in RM HA

Xuan Gong created YARN-1765: --- Summary: Write test cases to verify that killApplication API works in RM HA Key: YARN-1765 URL: https://issues.apache.org/jira/browse/YARN-1765 Project: Hadoop YARN

[jira] [Updated] (YARN-1765) Write test cases to verify that killApplication API works in RM HA

[ https://issues.apache.org/jira/browse/YARN-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1765: Attachment: YARN-1765.1.patch Write test cases to verify that killApplication API works in RM HA

[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-tabpanelfocusedCommentId=13912565#comment-13912565 ] Hudson commented on YARN-1561: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5226 (See

[jira] [Commented] (YARN-1765) Write test cases to verify that killApplication API works in RM HA

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