[jira] [Commented] (YARN-2075) TestRMAdminCLI consistently fail on trunk and branch-2

[ https://issues.apache.org/jira/browse/YARN-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015227#comment-14015227 ] Tsuyoshi OZAWA commented on YARN-2075: -- I could reproduce this problem on both trunk

[jira] [Commented] (YARN-1874) Cleanup: Move RMActiveServices out of ResourceManager into its own file

[ https://issues.apache.org/jira/browse/YARN-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015228#comment-14015228 ] Tsuyoshi OZAWA commented on YARN-1874: -- I found that the test failure is not related

[jira] [Resolved] (YARN-804) mark AbstractService init/start/stop methods as final

[ https://issues.apache.org/jira/browse/YARN-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-804. - Resolution: Won't Fix I don't think we can fix this while mocking is used to test some aspects of

[jira] [Updated] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1913: -- Attachment: YARN-1913.patch Thanks, Sandy. Upload a new patch, move the AM resource usage check to

[jira] [Commented] (YARN-2103) Inconsistency between viaProto flag and initial value of SerializedExceptionProto.Builder

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

[jira] [Commented] (YARN-741) Mark yarn.service package as public unstable

[ https://issues.apache.org/jira/browse/YARN-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015298#comment-14015298 ] Steve Loughran commented on YARN-741: - fixed in YARN-825 Mark yarn.service package as

[jira] [Resolved] (YARN-741) Mark yarn.service package as public unstable

[ https://issues.apache.org/jira/browse/YARN-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved YARN-741. - Resolution: Duplicate Mark yarn.service package as public unstable

[jira] [Commented] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

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

[jira] [Commented] (YARN-2103) Inconsistency between viaProto flag and initial value of SerializedExceptionProto.Builder

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

[jira] [Updated] (YARN-2117) Close of Reader in TimelineAuthenticationFilterInitializer#initFilter() should be enclosed in finally block

[ https://issues.apache.org/jira/browse/YARN-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-2117: -- Attachment: YARN-2117.patch Close of Reader in TimelineAuthenticationFilterInitializer#initFilter() should

[jira] [Updated] (YARN-2117) Close of Reader in TimelineAuthenticationFilterInitializer#initFilter() should be enclosed in finally block

[ https://issues.apache.org/jira/browse/YARN-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-2117: -- Attachment: YARN-2117.patch Close of Reader in TimelineAuthenticationFilterInitializer#initFilter() should

[jira] [Updated] (YARN-2117) Close of Reader in TimelineAuthenticationFilterInitializer#initFilter() should be enclosed in finally block

[ https://issues.apache.org/jira/browse/YARN-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen He updated YARN-2117: -- Attachment: (was: YARN-2117.patch) Close of Reader in TimelineAuthenticationFilterInitializer#initFilter()

[jira] [Commented] (YARN-2075) TestRMAdminCLI consistently fail on trunk and branch-2

[ https://issues.apache.org/jira/browse/YARN-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015401#comment-14015401 ] Mit Desai commented on YARN-2075: - [~ozawa] and [~kj-ki] that was my bad. My local repo

[jira] [Updated] (YARN-1874) Cleanup: Move RMActiveServices out of ResourceManager into its own file

[ https://issues.apache.org/jira/browse/YARN-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1874: - Attachment: YARN-1874.4.patch Cleanup: Move RMActiveServices out of ResourceManager into its own

[jira] [Updated] (YARN-1874) Cleanup: Move RMActiveServices out of ResourceManager into its own file

[ https://issues.apache.org/jira/browse/YARN-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi OZAWA updated YARN-1874: - Attachment: (was: YARN-1874.4.patch) Cleanup: Move RMActiveServices out of ResourceManager

[jira] [Commented] (YARN-2103) Inconsistency between viaProto flag and initial value of SerializedExceptionProto.Builder

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

[jira] [Updated] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1913: -- Attachment: YARN-1913.patch With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[jira] [Commented] (YARN-2103) Inconsistency between viaProto flag and initial value of SerializedExceptionProto.Builder

[ https://issues.apache.org/jira/browse/YARN-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015414#comment-14015414 ] Tsuyoshi OZAWA commented on YARN-2103: -- Thanks and good job, [~decster], and thanks

[jira] [Commented] (YARN-2075) TestRMAdminCLI consistently fail on trunk and branch-2

[ https://issues.apache.org/jira/browse/YARN-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015421#comment-14015421 ] Tsuyoshi OZAWA commented on YARN-2075: -- [~mitdesai], Thanks for reporitng. +1

[jira] [Commented] (YARN-2117) Close of Reader in TimelineAuthenticationFilterInitializer#initFilter() should be enclosed in finally block

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

[jira] [Assigned] (YARN-1550) NPE in FairSchedulerAppsBlock#render

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1550: -- Assignee: Anubhav Dhoot Looks good to me. +1. Committing this shortly. NPE in

[jira] [Commented] (YARN-1550) NPE in FairSchedulerAppsBlock#render

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015439#comment-14015439 ] Karthik Kambatla commented on YARN-1550: Actually, I run into the following NPE

[jira] [Commented] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

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

[jira] [Commented] (YARN-1874) Cleanup: Move RMActiveServices out of ResourceManager into its own file

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

[jira] [Commented] (YARN-2103) Inconsistency between viaProto flag and initial value of SerializedExceptionProto.Builder

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

[jira] [Commented] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015518#comment-14015518 ] Sandy Ryza commented on YARN-1913: -- This is looking good. A small things.

[jira] [Commented] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015536#comment-14015536 ] Wei Yan commented on YARN-1913: --- Thanks, Sandy. One problem may exist if we use

[jira] [Commented] (YARN-1874) Cleanup: Move RMActiveServices out of ResourceManager into its own file

[ https://issues.apache.org/jira/browse/YARN-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015588#comment-14015588 ] Tsuyoshi OZAWA commented on YARN-1874: -- It's ready for review. This patch includes

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015611#comment-14015611 ] Bikas Saha commented on YARN-2091: -- Can this miss a case when the exitCode has not been

[jira] [Created] (YARN-2119) Fix the DEFAULT_PROXY_ADDRESS used for getBindAddress to fix 1590

Anubhav Dhoot created YARN-2119: --- Summary: Fix the DEFAULT_PROXY_ADDRESS used for getBindAddress to fix 1590 Key: YARN-2119 URL: https://issues.apache.org/jira/browse/YARN-2119 Project: Hadoop YARN

[jira] [Created] (YARN-2120) Coloring queues running over minShare on RM Scheduler page

Siqi Li created YARN-2120: - Summary: Coloring queues running over minShare on RM Scheduler page Key: YARN-2120 URL: https://issues.apache.org/jira/browse/YARN-2120 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015653#comment-14015653 ] Karthik Kambatla commented on YARN-2010: Sorry, the commit messages are for the

[jira] [Updated] (YARN-2120) Coloring queues running over minShare on RM Scheduler page

[ https://issues.apache.org/jira/browse/YARN-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2120: -- Description: Today RM Scheduler page shows FairShare, Used, Used (over fair share) and MaxCapacity. Since

[jira] [Updated] (YARN-2120) Coloring queues running over minShare on RM Scheduler page

[ https://issues.apache.org/jira/browse/YARN-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2120: -- Attachment: AD45B623-9F14-420B-B1FB-1186E2B5EC4A.png Coloring queues running over minShare on RM Scheduler

[jira] [Updated] (YARN-2119) Fix the DEFAULT_PROXY_ADDRESS used for getBindAddress to fix 1590

[ https://issues.apache.org/jira/browse/YARN-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2119: Attachment: YARN-2119.patch Fix with unit tests. Ran

[jira] [Resolved] (YARN-2108) Show minShare on RM Fair Scheduler page

[ https://issues.apache.org/jira/browse/YARN-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li resolved YARN-2108. --- Resolution: Duplicate Show minShare on RM Fair Scheduler page ---

[jira] [Reopened] (YARN-2108) Show minShare on RM Fair Scheduler page

[ https://issues.apache.org/jira/browse/YARN-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li reopened YARN-2108: --- Show minShare on RM Fair Scheduler page --- Key:

[jira] [Commented] (YARN-2120) Coloring queues running over minShare on RM Scheduler page

[ https://issues.apache.org/jira/browse/YARN-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015732#comment-14015732 ] Siqi Li commented on YARN-2120: --- Attached screenshot for proposed coloring scheme Coloring

[jira] [Resolved] (YARN-2108) Show minShare on RM Fair Scheduler page

[ https://issues.apache.org/jira/browse/YARN-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li resolved YARN-2108. --- Resolution: Duplicate Show minShare on RM Fair Scheduler page ---

[jira] [Updated] (YARN-1550) NPE in FairSchedulerAppsBlock#render

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-1550: Attachment: YARN-1550.003.patch Fixed failures after resolving with some interim changes that were

[jira] [Created] (YARN-2121) TimelineAuthenticator#hasDelegationToken may throw NPE

Zhijie Shen created YARN-2121: - Summary: TimelineAuthenticator#hasDelegationToken may throw NPE Key: YARN-2121 URL: https://issues.apache.org/jira/browse/YARN-2121 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1913: -- Attachment: YARN-1913.patch Update a patch. Use getLiveContainer().size() and unManagedAM to detect the AM

[jira] [Commented] (YARN-2119) Fix the DEFAULT_PROXY_ADDRESS used for getBindAddress to fix 1590

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

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015776#comment-14015776 ] Vinod Kumar Vavilapalli commented on YARN-2010: --- bq. It is true that the

[jira] [Commented] (YARN-1550) NPE in FairSchedulerAppsBlock#render

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

[jira] [Updated] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1913: -- Attachment: YARN-1913.patch Thanks, Sandy. Fixed that problem. With Fair Scheduler, cluster can logjam when

[jira] [Commented] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

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

[jira] [Updated] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-1913: -- Attachment: YARN-1913.patch New patch to fix the test errors. With Fair Scheduler, cluster can logjam when

[jira] [Commented] (YARN-1550) NPE in FairSchedulerAppsBlock#render

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015844#comment-14015844 ] Karthik Kambatla commented on YARN-1550: Thanks Anubhav. +1. Committing this

[jira] [Commented] (YARN-1590) _HOST doesn't expand properly for RM, NM, ProxyServer and JHS

[ https://issues.apache.org/jira/browse/YARN-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015862#comment-14015862 ] Karthik Kambatla commented on YARN-1590: Just ran into this. If I am not mistaken,

[jira] [Commented] (YARN-2119) Fix the DEFAULT_PROXY_ADDRESS used for getBindAddress to fix 1590

[ https://issues.apache.org/jira/browse/YARN-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015866#comment-14015866 ] Karthik Kambatla commented on YARN-2119: Looks good to me. +1. I ll commit this

[jira] [Commented] (YARN-1877) Document yarn.resourcemanager.zk-auth and its scope

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

[jira] [Commented] (YARN-1550) NPE in FairSchedulerAppsBlock#render

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

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

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

[jira] [Resolved] (YARN-1540) Add an easy way to turn on HA

[ https://issues.apache.org/jira/browse/YARN-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-1540. Resolution: Invalid Target Version/s: (was: ) Other sub-tasks under YARN-149

[jira] [Commented] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

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

[jira] [Created] (YARN-2122) In AllocationFileLoaderService, the reloadThread should be created in init() and started in start()

Karthik Kambatla created YARN-2122: -- Summary: In AllocationFileLoaderService, the reloadThread should be created in init() and started in start() Key: YARN-2122 URL:

[jira] [Commented] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

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

[jira] [Updated] (YARN-2120) Coloring queues running over minShare on RM Scheduler page

[ https://issues.apache.org/jira/browse/YARN-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2120: -- Attachment: YARN-2120.v1.patch Coloring queues running over minShare on RM Scheduler page

[jira] [Updated] (YARN-2121) TimelineAuthenticator#hasDelegationToken may throw NPE

[ https://issues.apache.org/jira/browse/YARN-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2121: -- Attachment: YARN-2121.1.patch Upload a patch to fix the problem, and add the corresponding test cases.

[jira] [Updated] (YARN-2122) In AllocationFileLoaderService, the reloadThread should be created in init() and started in start()

[ https://issues.apache.org/jira/browse/YARN-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-2122: Attachment: YARN-2122.patch In AllocationFileLoaderService, the reloadThread should be created in

[jira] [Commented] (YARN-2120) Coloring queues running over minShare on RM Scheduler page

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

[jira] [Commented] (YARN-2122) In AllocationFileLoaderService, the reloadThread should be created in init() and started in start()

[ https://issues.apache.org/jira/browse/YARN-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015986#comment-14015986 ] Tsuyoshi OZAWA commented on YARN-2122: -- Thank you for taking this JIRA, [~rkanter]. I

[jira] [Commented] (YARN-2121) TimelineAuthenticator#hasDelegationToken may throw NPE

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

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016019#comment-14016019 ] Tsuyoshi OZAWA commented on YARN-2091: -- [~bikassaha], thank you for the comments.

[jira] [Commented] (YARN-2120) Coloring queues running over minShare on RM Scheduler page

[ https://issues.apache.org/jira/browse/YARN-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016027#comment-14016027 ] Ashwin Shankar commented on YARN-2120: -- [~l201514], It would be helpful if we don't

[jira] [Commented] (YARN-2122) In AllocationFileLoaderService, the reloadThread should be created in init() and started in start()

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

[jira] [Commented] (YARN-2122) In AllocationFileLoaderService, the reloadThread should be created in init() and started in start()

[ https://issues.apache.org/jira/browse/YARN-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016035#comment-14016035 ] Karthik Kambatla commented on YARN-2122: Good point, [~ozawa]. It would definitely

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016050#comment-14016050 ] Ashwin Shankar commented on YARN-2026: -- Hi [~sandyr], did you have any comments ?

[jira] [Commented] (YARN-2120) Coloring queues running over minShare on RM Scheduler page

[ https://issues.apache.org/jira/browse/YARN-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016066#comment-14016066 ] Siqi Li commented on YARN-2120: --- [~ashwinshankar77] thanks for your feedback, let me see if I

[jira] [Commented] (YARN-2122) In AllocationFileLoaderService, the reloadThread should be created in init() and started in start()

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

[jira] [Commented] (YARN-2091) Add ContainerExitStatus.KILL_EXCEEDED_MEMORY and pass it to app masters

[ https://issues.apache.org/jira/browse/YARN-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016081#comment-14016081 ] Bikas Saha commented on YARN-2091: -- If we are sure that the default value is set in the

[jira] [Commented] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

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

[jira] [Commented] (YARN-2022) Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy

[ https://issues.apache.org/jira/browse/YARN-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016151#comment-14016151 ] Carlo Curino commented on YARN-2022: Hi Sunil, I read the doc with [~chris.douglas] and

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016155#comment-14016155 ] Sandy Ryza commented on YARN-2026: -- Hi Ashwin, have been busy with other stuff and

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016191#comment-14016191 ] Ashwin Shankar commented on YARN-2026: -- [~sandyr], Sure Sandy I'll patiently wait for