[jira] [Commented] (YARN-315) Use security token protobuf definition from hadoop common

[ https://issues.apache.org/jira/browse/YARN-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546773#comment-13546773 ] Hudson commented on YARN-315: - Integrated in Hadoop-Yarn-trunk #90 (See [https://builds.apache.

[jira] [Commented] (YARN-170) NodeManager stop() gets called twice on shutdown

[ https://issues.apache.org/jira/browse/YARN-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546776#comment-13546776 ] Hudson commented on YARN-170: - Integrated in Hadoop-Yarn-trunk #90 (See [https://builds.apache.

[jira] [Moved] (YARN-321) Generic application history service

[ https://issues.apache.org/jira/browse/YARN-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli moved MAPREDUCE-3061 to YARN-321: - Tags: (was: mrv2, history server)

[jira] [Updated] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-2: - Attachment: YARN-2.patch > Enhance CS to schedule accounting for both memory and cpu cores >

[jira] [Created] (YARN-322) Add cpu information to queue metrics

Arun C Murthy created YARN-322: -- Summary: Add cpu information to queue metrics Key: YARN-322 URL: https://issues.apache.org/jira/browse/YARN-322 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546824#comment-13546824 ] Arun C Murthy commented on YARN-2: -- Fixed TestRMWebServicesCapacitySched (had to fix the test

[jira] [Updated] (YARN-253) Container launch may fail if no files were localized

[ https://issues.apache.org/jira/browse/YARN-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-253: - Attachment: YARN-253-20130108.txt Same patch without TestDistributedShell changes

[jira] [Commented] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

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

[jira] [Commented] (YARN-253) Container launch may fail if no files were localized

s of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12563743/YARN-253-20130108.txt against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to inclu

[jira] [Commented] (YARN-170) NodeManager stop() gets called twice on shutdown

[ https://issues.apache.org/jira/browse/YARN-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546866#comment-13546866 ] Hudson commented on YARN-170: - Integrated in Hadoop-Hdfs-trunk #1279 (See [https://builds.apach

[jira] [Commented] (YARN-253) Container launch may fail if no files were localized

ee: Tom White >Priority: Critical > Fix For: 2.0.3-alpha > > Attachments: YARN-253-20130108.txt, YARN-253.patch, YARN-253.patch, > YARN-253-test.patch > > > This can be demonstrated with DistributedShell. The containers running the > shell do not have a

[jira] [Created] (YARN-323) Yarn CLI commands prints classpath

Nishan Shetty created YARN-323: -- Summary: Yarn CLI commands prints classpath Key: YARN-323 URL: https://issues.apache.org/jira/browse/YARN-323 Project: Hadoop YARN Issue Type: Bug Affects Ve

[jira] [Commented] (YARN-315) Use security token protobuf definition from hadoop common

[ https://issues.apache.org/jira/browse/YARN-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546900#comment-13546900 ] Hudson commented on YARN-315: - Integrated in Hadoop-Mapreduce-trunk #1307 (See [https://builds.

[jira] [Commented] (YARN-170) NodeManager stop() gets called twice on shutdown

[ https://issues.apache.org/jira/browse/YARN-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546903#comment-13546903 ] Hudson commented on YARN-170: - Integrated in Hadoop-Mapreduce-trunk #1307 (See [https://builds.

[jira] [Commented] (YARN-217) yarn rmadmin commands fail in secure cluster

[ https://issues.apache.org/jira/browse/YARN-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546907#comment-13546907 ] Hudson commented on YARN-217: - Integrated in Hadoop-Mapreduce-trunk #1307 (See [https://builds.

[jira] [Resolved] (YARN-318) sendSignal in DefaultContainerExecutor causes "invalid options" error

[ https://issues.apache.org/jira/browse/YARN-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hyunsik Choi resolved YARN-318. --- Resolution: Not A Problem I didn't doubt the kill's bug because it is very common utility and it worked

[jira] [Commented] (YARN-320) RM should always be able to renew its own tokens

[ https://issues.apache.org/jira/browse/YARN-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13546988#comment-13546988 ] Daryn Sharp commented on YARN-320: -- Admittedly, extracting the renewer is a bit dubious. I

[jira] [Updated] (YARN-309) Make RM provide heartbeat interval to NM

[ https://issues.apache.org/jira/browse/YARN-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-309: --- Attachment: YARN-309.2.patch > Make RM provide heartbeat interval to NM > -

[jira] [Updated] (YARN-320) RM should always be able to renew its own tokens

[ https://issues.apache.org/jira/browse/YARN-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated YARN-320: - Attachment: YARN-320.branch-23.patch Add unit tests, trunk patch forthcoming. > RM should

[jira] [Updated] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-193: - Attachment: YARN-193.4.patch Re-based patch against latest code. > Scheduler.normalizeReq

[jira] [Created] (YARN-324) Provide way to preserve

Lohit Vijayarenu created YARN-324: - Summary: Provide way to preserve Key: YARN-324 URL: https://issues.apache.org/jira/browse/YARN-324 Project: Hadoop YARN Issue Type: Bug Componen

[jira] [Updated] (YARN-324) Provide way to preserve container directories

[ https://issues.apache.org/jira/browse/YARN-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lohit Vijayarenu updated YARN-324: -- Summary: Provide way to preserve container directories (was: Provide way to preserve ) > Pr

[jira] [Commented] (YARN-324) Provide way to preserve container directories

[ https://issues.apache.org/jira/browse/YARN-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547191#comment-13547191 ] Jason Lowe commented on YARN-324: - The nodemanager currently supports this via the yarn.nod

[jira] [Updated] (YARN-320) RM should always be able to renew its own tokens

[ https://issues.apache.org/jira/browse/YARN-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated YARN-320: - Attachment: YARN-320.patch Patch for trunk and branch-2. > RM should always be able to ren

[jira] [Commented] (YARN-320) RM should always be able to renew its own tokens

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

[jira] [Commented] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

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

[jira] [Updated] (YARN-193) Scheduler.normalizeRequest does not account for allocation requests that exceed maximumAllocation limits

[ https://issues.apache.org/jira/browse/YARN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-193: - Affects Version/s: (was: 2.0.3-alpha) 2.0.2-alpha > Scheduler.normalizeReque

[jira] [Created] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

Jason Lowe created YARN-325: --- Summary: RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing Key: YARN-325 URL: https://issues.apache.org/jira/browse/YARN-325 Project

[jira] [Commented] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547409#comment-13547409 ] Jason Lowe commented on YARN-325: - Stacktrace of an occurrence: {noformat} "IPC Server hand

[jira] [Updated] (YARN-142) Change YARN APIs to throw IOException

[ https://issues.apache.org/jira/browse/YARN-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-142: --- Attachment: YARN-142.3.patch > Change YARN APIs to throw IOException >

[jira] [Commented] (YARN-309) Make RM provide heartbeat interval to NM

[ https://issues.apache.org/jira/browse/YARN-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547576#comment-13547576 ] Bikas Saha commented on YARN-309: - I see the config being really a minimum value and not the

[jira] [Updated] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-2: - Attachment: YARN-2.patch > Enhance CS to schedule accounting for both memory and cpu cores >

[jira] [Commented] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

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

[jira] [Commented] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

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

[jira] [Commented] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

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

[jira] [Commented] (YARN-2) Enhance CS to schedule accounting for both memory and cpu cores

[ https://issues.apache.org/jira/browse/YARN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547664#comment-13547664 ] caolong commented on YARN-2: en，The great patch. all right,What are we planning to do ahout FairSc

[jira] [Commented] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547673#comment-13547673 ] Arun C Murthy commented on YARN-325: [~jlowe] This seems limited to a corner case (not t

[jira] [Assigned] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy reassigned YARN-325: -- Assignee: Arun C Murthy > RM CapacityScheduler can deadlock when getQueueInfo() is called and

[jira] [Updated] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-325: --- Priority: Blocker (was: Critical) > RM CapacityScheduler can deadlock when getQueueInfo() is calle

[jira] [Commented] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547677#comment-13547677 ] Arun C Murthy commented on YARN-325: Ok, the fix is to bubble the 'non-requirement' of t

[jira] [Updated] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-325: --- Attachment: YARN-325.patch Illustrative patch, need to fix unit-tests yet. > RM Capaci

[jira] [Updated] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

[ https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-325: --- Attachment: YARN-325.patch Added unit-tests. > RM CapacityScheduler can deadlock when

[jira] [Commented] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

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