[jira] [Created] (YARN-2602) Generic History Service of TimelineServer sometimes not able to handle NPE

Karam Singh created YARN-2602: - Summary: Generic History Service of TimelineServer sometimes not able to handle NPE Key: YARN-2602 URL: https://issues.apache.org/jira/browse/YARN-2602 Project: Hadoop

[jira] [Commented] (YARN-2602) Generic History Service of TimelineServer sometimes not able to handle NPE

[ https://issues.apache.org/jira/browse/YARN-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147453#comment-14147453 ] Karam Singh commented on YARN-2602: --- Following is Stack Trace from TimelineServer {code}

[jira] [Assigned] (YARN-2602) Generic History Service of TimelineServer sometimes not able to handle NPE

[ https://issues.apache.org/jira/browse/YARN-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen reassigned YARN-2602: - Assignee: Zhijie Shen Generic History Service of TimelineServer sometimes not able to handle NPE

[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields

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

[jira] [Commented] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

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

[jira] [Resolved] (YARN-2590) Windows Secure Container Executor: containerLaunch environment does not get transferred to the container process

[ https://issues.apache.org/jira/browse/YARN-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu resolved YARN-2590. Resolution: Cannot Reproduce Environment gets passed to container via the launch_container.cmd @set

[jira] [Commented] (YARN-2102) More generalized timeline ACLs

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

[jira] [Commented] (YARN-2161) Fix build on macosx: YARN parts

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

[jira] [Commented] (YARN-2596) TestWorkPreservingRMRestart fails with FairScheduler

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

[jira] [Commented] (YARN-2546) REST API for application creation/submission is using strings for numeric boolean values

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

[jira] [Commented] (YARN-2581) NMs need to find a way to get LogAggregationContext

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

[jira] [Updated] (YARN-2391) Windows Secure Container Executor helper service should assign launched process to the NM job

[ https://issues.apache.org/jira/browse/YARN-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2391: --- Attachment: YARN-2391.1.patch Fix by adding an optional

[jira] [Resolved] (YARN-2391) Windows Secure Container Executor helper service should assign launched process to the NM job

[ https://issues.apache.org/jira/browse/YARN-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu resolved YARN-2391. Resolution: Implemented Windows Secure Container Executor helper service should assign launched

[jira] [Commented] (YARN-2391) Windows Secure Container Executor helper service should assign launched process to the NM job

[ https://issues.apache.org/jira/browse/YARN-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147678#comment-14147678 ] Remus Rusanu commented on YARN-2391: The patch will be included in next YARN-2198 patch

[jira] [Commented] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

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

[jira] [Updated] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2198: --- Attachment: YARN-2198.trunk.10.patch .trunk.10.patch contains the fixes for YARN-2391, YARN-2580,

[jira] [Updated] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2198: --- Attachment: (was: YARN-2198.trunk.10.patch) Remove the need to run NodeManager as privileged

[jira] [Commented] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

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

[jira] [Updated] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2198: --- Attachment: (was: YARN-2198.trunk.10.patch) Remove the need to run NodeManager as privileged

[jira] [Updated] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2198: --- Attachment: YARN-2198.trunk.10.patch Remove the need to run NodeManager as privileged account for

[jira] [Commented] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

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

[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 attaching the same patch to kick jenkins. CapacityScheduler: Improve

[jira] [Updated] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2198: --- Attachment: (was: YARN-2198.trunk.10.patch) Remove the need to run NodeManager as privileged

[jira] [Updated] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2198: --- Attachment: YARN-2198.trunk.10.patch Remove the need to run NodeManager as privileged account for

[jira] [Updated] (YARN-2494) [YARN-796] Node label manager API and storage implementations

[ https://issues.apache.org/jira/browse/YARN-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2494: - Attachment: YARN-2494.patch Attached new patch [YARN-796] Node label manager API and storage

[jira] [Commented] (YARN-2102) More generalized timeline ACLs

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

[jira] [Commented] (YARN-2546) REST API for application creation/submission is using strings for numeric boolean values

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

[jira] [Commented] (YARN-2596) TestWorkPreservingRMRestart fails with FairScheduler

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

[jira] [Commented] (YARN-2581) NMs need to find a way to get LogAggregationContext

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

[jira] [Commented] (YARN-2161) Fix build on macosx: YARN parts

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

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

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

[jira] [Commented] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

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

[jira] [Issue Comment Deleted] (YARN-1964) Create Docker analog of the LinuxContainerExecutor in YARN

[ https://issues.apache.org/jira/browse/YARN-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-1964: --- Comment: was deleted (was: Pull-request on git:

[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 Update tests for handle SystemMetricsPublisher CapacityScheduler:

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

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

[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 fix patch CapacityScheduler: Improve reservations

[jira] [Created] (YARN-2603) ApplicationConstants missing HADOOP_MAPRED_HOME

Allen Wittenauer created YARN-2603: -- Summary: ApplicationConstants missing HADOOP_MAPRED_HOME Key: YARN-2603 URL: https://issues.apache.org/jira/browse/YARN-2603 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node

[ https://issues.apache.org/jira/browse/YARN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147878#comment-14147878 ] Karthik Kambatla commented on YARN-2604: The scheduler can use

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

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

[jira] [Created] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node

Karthik Kambatla created YARN-2604: -- Summary: Scheduler should consider max-allocation-* in conjunction with the largest node Key: YARN-2604 URL: https://issues.apache.org/jira/browse/YARN-2604

[jira] [Commented] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node

[ https://issues.apache.org/jira/browse/YARN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147899#comment-14147899 ] Jason Lowe commented on YARN-2604: -- How is this different from YARN-56? Also wondering

[jira] [Resolved] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node

[ https://issues.apache.org/jira/browse/YARN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-2604. Resolution: Duplicate Thanks for pointing out YARN-56, Jason. Closing this as a duplicate.

[jira] [Assigned] (YARN-56) Handle container requests that request more resources than currently available in the cluster

[ https://issues.apache.org/jira/browse/YARN-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-56: Assignee: Karthik Kambatla Handle container requests that request more resources than

[jira] [Commented] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node

[ https://issues.apache.org/jira/browse/YARN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147934#comment-14147934 ] Karthik Kambatla commented on YARN-2604: Actually, I think the JIRA here is

[jira] [Commented] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node

[ https://issues.apache.org/jira/browse/YARN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147942#comment-14147942 ] Jason Lowe commented on YARN-2604: -- Ah, I see, yes they're a little bit different. They'd

[jira] [Commented] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147946#comment-14147946 ] Remus Rusanu commented on YARN-2198: Core test failure is: {code} Tests run: 7,

[jira] [Commented] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147952#comment-14147952 ] Remus Rusanu commented on YARN-2198: The findbugs warning is {code} Inconsistent

[jira] [Commented] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147955#comment-14147955 ] Jian He commented on YARN-2523: --- +1 for the latest patch. ResourceManager UI showing

[jira] [Commented] (YARN-2581) NMs need to find a way to get LogAggregationContext

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

[jira] [Commented] (YARN-2596) TestWorkPreservingRMRestart fails with FairScheduler

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

[jira] [Commented] (YARN-2546) REST API for application creation/submission is using strings for numeric boolean values

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

[jira] [Commented] (YARN-2161) Fix build on macosx: YARN parts

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

[jira] [Commented] (YARN-2102) More generalized timeline ACLs

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

[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 CapacityScheduler: Improve reservations

[jira] [Reopened] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node

[ https://issues.apache.org/jira/browse/YARN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reopened YARN-2604: Scheduler should consider max-allocation-* in conjunction with the largest node

[jira] [Commented] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node

[ https://issues.apache.org/jira/browse/YARN-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148003#comment-14148003 ] Karthik Kambatla commented on YARN-2604: bq. I guess it comes down to whether we

[jira] [Commented] (YARN-2594) ResourceManger sometimes become un-responsive

[ https://issues.apache.org/jira/browse/YARN-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148006#comment-14148006 ] Karthik Kambatla commented on YARN-2594: Taking a look at the issue and the patch..

[jira] [Commented] (YARN-2594) ResourceManger sometimes become un-responsive

[ https://issues.apache.org/jira/browse/YARN-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148049#comment-14148049 ] Karthik Kambatla commented on YARN-2594: Thanks for working on this, Wangda. As I

[jira] [Updated] (YARN-2594) Potential deadlock in RM when querying ApplicationResourceUsageReport

[ https://issues.apache.org/jira/browse/YARN-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2594: --- Summary: Potential deadlock in RM when querying ApplicationResourceUsageReport (was:

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

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

[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields

[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148074#comment-14148074 ] Vinod Kumar Vavilapalli commented on YARN-668: -- Quick look at the patch - None

[jira] [Commented] (YARN-2494) [YARN-796] Node label manager API and storage implementations

[ https://issues.apache.org/jira/browse/YARN-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148094#comment-14148094 ] Craig Welch commented on YARN-2494: --- -re I suggest to change addLabels to addNodeLabels

[jira] [Commented] (YARN-2494) [YARN-796] Node label manager API and storage implementations

[ https://issues.apache.org/jira/browse/YARN-2494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148095#comment-14148095 ] Craig Welch commented on YARN-2494: --- ...other kinds of labels..., rather [YARN-796]

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

[ https://issues.apache.org/jira/browse/YARN-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148098#comment-14148098 ] Thomas Graves commented on YARN-1769: - We've been running this now on cluster for quite

[jira] [Created] (YARN-2605) [RM HA] Rest api endpoints doing redirect incorrectly

bc Wong created YARN-2605: - Summary: [RM HA] Rest api endpoints doing redirect incorrectly Key: YARN-2605 URL: https://issues.apache.org/jira/browse/YARN-2605 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields

[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148125#comment-14148125 ] Jian He commented on YARN-668: -- - containerManagerImpl, TestApplicationMasterService changes

[jira] [Commented] (YARN-2523) ResourceManager UI showing negative value for Decommissioned Nodes field

[ https://issues.apache.org/jira/browse/YARN-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148135#comment-14148135 ] Jian He commented on YARN-2523: --- [~jlowe], would you like to take another look ?

[jira] [Commented] (YARN-2601) RMs(HA RMS) can't enter active state

[ https://issues.apache.org/jira/browse/YARN-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148155#comment-14148155 ] Aroop Maliakkal commented on YARN-2601: --- As a workaround, we deleted the entries in

[jira] [Updated] (YARN-1963) Support priorities across applications within the same queue

[ https://issues.apache.org/jira/browse/YARN-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-1963: -- Attachment: YARN Application Priorities Design.pdf Hi All I am uploading an initial draft for Application

[jira] [Updated] (YARN-2179) Initial cache manager structure and context

[ https://issues.apache.org/jira/browse/YARN-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated YARN-2179: --- Attachment: YARN-2179-trunk-v7.patch Slight update. AppChecker and RemoteAppChecker are now a service

[jira] [Updated] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2198: --- Attachment: (was: YARN-2198.trunk.10.patch) Remove the need to run NodeManager as privileged

[jira] [Updated] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

[ https://issues.apache.org/jira/browse/YARN-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remus Rusanu updated YARN-2198: --- Attachment: YARN-2198.trunk.10.patch Remove the need to run NodeManager as privileged account for

[jira] [Updated] (YARN-2180) In-memory backing store for cache manager

[ https://issues.apache.org/jira/browse/YARN-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Trezzo updated YARN-2180: --- Attachment: YARN-2180-trunk-v4.patch [~kasha] [~vinodkv] [~sjlee0] Attached is v4. Here are some

[jira] [Commented] (YARN-2179) Initial cache manager structure and context

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

[jira] [Created] (YARN-2606) Application History Server tries to access hdfs before doing secure login

Mit Desai created YARN-2606: --- Summary: Application History Server tries to access hdfs before doing secure login Key: YARN-2606 URL: https://issues.apache.org/jira/browse/YARN-2606 Project: Hadoop YARN

[jira] [Updated] (YARN-2606) Application History Server tries to access hdfs before doing secure login

[ https://issues.apache.org/jira/browse/YARN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated YARN-2606: Component/s: timelineserver Application History Server tries to access hdfs before doing secure login

[jira] [Updated] (YARN-2606) Application History Server tries to access hdfs before doing secure login

[ https://issues.apache.org/jira/browse/YARN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mit Desai updated YARN-2606: Attachment: YARN-2606.patch Attaching the patch. Application History Server tries to access hdfs before

[jira] [Created] (YARN-2607) TestDistributedShell fails in trunk

Ted Yu created YARN-2607: Summary: TestDistributedShell fails in trunk Key: YARN-2607 URL: https://issues.apache.org/jira/browse/YARN-2607 Project: Hadoop YARN Issue Type: Test Reporter:

[jira] [Commented] (YARN-2606) Application History Server tries to access hdfs before doing secure login

[ https://issues.apache.org/jira/browse/YARN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148255#comment-14148255 ] Zhijie Shen commented on YARN-2606: --- The right fix may be moving the FS operations to

[jira] [Commented] (YARN-2198) Remove the need to run NodeManager as privileged account for Windows Secure Container Executor

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

[jira] [Updated] (YARN-913) Add a way to register long-lived services in a YARN cluster

[ https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-913: Attachment: YARN-913-010.patch This patch doesn't look at why yesterday's jenkin tests failed, so if

[jira] [Commented] (YARN-2606) Application History Server tries to access hdfs before doing secure login

[ https://issues.apache.org/jira/browse/YARN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148273#comment-14148273 ] Jonathan Eagles commented on YARN-2606: --- I can see this both ways. It seems to

[jira] [Created] (YARN-2608) FairScheduler may hung due to two potential deadlocks

Wei Yan created YARN-2608: - Summary: FairScheduler may hung due to two potential deadlocks Key: YARN-2608 URL: https://issues.apache.org/jira/browse/YARN-2608 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-2606) Application History Server tries to access hdfs before doing secure login

[ https://issues.apache.org/jira/browse/YARN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148278#comment-14148278 ] Zhijie Shen commented on YARN-2606: --- [~jeagles], I saw doSecureLogin is invoked at start

[jira] [Updated] (YARN-2608) FairScheduler may hung due to two potential deadlocks

[ https://issues.apache.org/jira/browse/YARN-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2608: -- Attachment: YARN-2608-1.patch FairScheduler may hung due to two potential deadlocks

[jira] [Commented] (YARN-2606) Application History Server tries to access hdfs before doing secure login

[ https://issues.apache.org/jira/browse/YARN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148282#comment-14148282 ] Mit Desai commented on YARN-2606: - Thanks for the the suggestion [~zjshen]. Moving the FS

[jira] [Commented] (YARN-2606) Application History Server tries to access hdfs before doing secure login

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

[jira] [Updated] (YARN-2608) FairScheduler may hung due to two potential deadlocks

[ https://issues.apache.org/jira/browse/YARN-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2608: -- Description: Two potential deadlocks exist inside the FairScheduler. 1. AllocationFileLoaderService would reload

[jira] [Updated] (YARN-1051) YARN Admission Control/Planner: enhancing the resource allocation model with time.

[ https://issues.apache.org/jira/browse/YARN-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-1051: - Attachment: YARN-1051.patch I am attaching a merge patch with trunk for easy reference. This patch

[jira] [Commented] (YARN-2608) FairScheduler may hung due to two potential deadlocks

[ https://issues.apache.org/jira/browse/YARN-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148302#comment-14148302 ] Wei Yan commented on YARN-2608: --- For the first deadlock, as the clock is only changed by

[jira] [Updated] (YARN-668) TokenIdentifier serialization should consider Unknown fields

[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-668: Attachment: YARN-668-v8.patch TokenIdentifier serialization should consider Unknown fields

[jira] [Commented] (YARN-2606) Application History Server tries to access hdfs before doing secure login

[ https://issues.apache.org/jira/browse/YARN-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148315#comment-14148315 ] Jonathan Eagles commented on YARN-2606: --- I don't have any context why login is part

[jira] [Commented] (YARN-668) TokenIdentifier serialization should consider Unknown fields

[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148326#comment-14148326 ] Junping Du commented on YARN-668: - Thanks [~vinodkv] and [~jianhe] for review and comments!

[jira] [Commented] (YARN-2608) FairScheduler may hung due to two potential deadlocks

[ https://issues.apache.org/jira/browse/YARN-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148328#comment-14148328 ] Karthik Kambatla commented on YARN-2608: Nit: Nothing to do with this patch, can we

[jira] [Comment Edited] (YARN-668) TokenIdentifier serialization should consider Unknown fields

[ https://issues.apache.org/jira/browse/YARN-668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148074#comment-14148074 ] Vinod Kumar Vavilapalli edited comment on YARN-668 at 9/25/14 9:19 PM:

[jira] [Updated] (YARN-2608) FairScheduler may hung due to two potential deadlocks

[ https://issues.apache.org/jira/browse/YARN-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-2608: -- Attachment: YARN-2608-2.patch FairScheduler may hung due to two potential deadlocks

[jira] [Commented] (YARN-2602) Generic History Service of TimelineServer sometimes not able to handle NPE

[ https://issues.apache.org/jira/browse/YARN-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148348#comment-14148348 ] Zhijie Shen commented on YARN-2602: --- The problem is that YARN_APPLICATION_VIEW_ACLS field

[jira] [Commented] (YARN-2608) FairScheduler may hung due to two potential deadlocks

[ https://issues.apache.org/jira/browse/YARN-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148354#comment-14148354 ] Karthik Kambatla commented on YARN-2608: +1, pending Jenkins. FairScheduler may

[jira] [Commented] (YARN-2550) TestAMRestart fails intermittently

[ https://issues.apache.org/jira/browse/YARN-2550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14148376#comment-14148376 ] Jason Lowe commented on YARN-2550: -- This looks like a dup of YARN-2483. TestAMRestart

[jira] [Commented] (YARN-2608) FairScheduler may hung due to two potential deadlocks

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

  1   2   >