[jira] [Moved] (YARN-570) Time strings are formated in different timezone

[ https://issues.apache.org/jira/browse/YARN-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J moved MAPREDUCE-5141 to YARN-570: - Key: YARN-570 (was: MAPREDUCE-5141) Project: Hadoop YARN (was: Hadoop Map/

[jira] [Updated] (YARN-441) Clean up unused collection methods in various APIs

[ https://issues.apache.org/jira/browse/YARN-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-441: --- Attachment: YARN-441.5.patch 1. fix -1 on javadoc 2. fix -1 on findbug by remove the keyword synchronized from

[jira] [Commented] (YARN-570) Time strings are formated in different timezone

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

[jira] [Commented] (YARN-441) Clean up unused collection methods in various APIs

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

[jira] [Commented] (YARN-570) Time strings are formated in different timezone

[ https://issues.apache.org/jira/browse/YARN-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629907#comment-13629907 ] Harsh J commented on YARN-570: -- Thanks for the report and the patch! With this patch it now re

[jira] [Updated] (YARN-457) Setting updated nodes from null to null causes NPE in AllocateResponsePBImpl

[ https://issues.apache.org/jira/browse/YARN-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenji Kikushima updated YARN-457: - Attachment: YARN-457-4.patch Attached a patch for trunk. Thank you. > Setting upda

[jira] [Commented] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

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

[jira] [Commented] (YARN-319) Submit a job to a queue that not allowed in fairScheduler, client will hold forever.

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

[jira] [Commented] (YARN-412) FifoScheduler incorrectly checking for node locality

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

[jira] [Commented] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

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

[jira] [Commented] (YARN-319) Submit a job to a queue that not allowed in fairScheduler, client will hold forever.

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

[jira] [Commented] (YARN-160) nodemanagers should obtain cpu/memory values from underlying OS

[ https://issues.apache.org/jira/browse/YARN-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630059#comment-13630059 ] Timothy St. Clair commented on YARN-160: If it's possible to tag along development o

[jira] [Commented] (YARN-412) FifoScheduler incorrectly checking for node locality

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

[jira] [Commented] (YARN-486) Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land

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

[jira] [Commented] (YARN-319) Submit a job to a queue that not allowed in fairScheduler, client will hold forever.

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

[jira] [Commented] (YARN-514) Delayed store operations should not result in RM unavailability for app submission

[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630320#comment-13630320 ] Bikas Saha commented on YARN-514: - you only need to add the new field in the enum. I dont th

[jira] [Created] (YARN-571) User should not be part of ContainerLaunchContext

Hitesh Shah created YARN-571: Summary: User should not be part of ContainerLaunchContext Key: YARN-571 URL: https://issues.apache.org/jira/browse/YARN-571 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-571) User should not be part of ContainerLaunchContext

[ https://issues.apache.org/jira/browse/YARN-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-571: - Issue Type: Sub-task (was: Bug) Parent: YARN-386 > User should not be part of ContainerLaunchC

[jira] [Created] (YARN-572) Remove duplication of data in Container

Hitesh Shah created YARN-572: Summary: Remove duplication of data in Container Key: YARN-572 URL: https://issues.apache.org/jira/browse/YARN-572 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-457) Setting updated nodes from null to null causes NPE in AllocateResponsePBImpl

[ https://issues.apache.org/jira/browse/YARN-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630425#comment-13630425 ] Xuan Gong commented on YARN-457: +1, Looks good > Setting updated nodes fro

[jira] [Assigned] (YARN-513) Verify all clients will wait for RM to restart

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-513: -- Assignee: Xuan Gong (was: Jian He) > Verify all clients will wait for RM to restart > --

[jira] [Commented] (YARN-392) Make it possible to schedule to specific nodes without dropping locality

[ https://issues.apache.org/jira/browse/YARN-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630440#comment-13630440 ] Sandy Ryza commented on YARN-392: - Any further thoughts on this? > Make it

[jira] [Updated] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

[ https://issues.apache.org/jira/browse/YARN-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-530: Attachment: YARN-530.4.patch no tangible change than previously; publishing to keep in sync with the

[jira] [Updated] (YARN-117) Enhance YARN service model

[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran updated YARN-117: Attachment: YARN-117.4.patch The changes here since the last patch related to the test {{TestNodeSta

[jira] [Commented] (YARN-117) Enhance YARN service model

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

[jira] [Commented] (YARN-530) Define Service model strictly, implement AbstractService for robust subclassing, migrate yarn-common services

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

[jira] [Commented] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630493#comment-13630493 ] Vinod Kumar Vavilapalli commented on YARN-561: -- Xuan, what Hitesh is saying is

[jira] [Assigned] (YARN-571) User should not be part of ContainerLaunchContext

[ https://issues.apache.org/jira/browse/YARN-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-571: Assignee: Vinod Kumar Vavilapalli Taking a shot at this.. >

[jira] [Assigned] (YARN-572) Remove duplication of data in Container

[ https://issues.apache.org/jira/browse/YARN-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah reassigned YARN-572: Assignee: Hitesh Shah > Remove duplication of data in Container > --

[jira] [Assigned] (YARN-435) Make it easier to access cluster topology information in an AM

[ https://issues.apache.org/jira/browse/YARN-435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah reassigned YARN-435: Assignee: Hitesh Shah > Make it easier to access cluster topology information in an AM >

[jira] [Commented] (YARN-503) DelegationTokens will be renewed forever if multiple jobs share tokens and the first one sets JOB_CANCEL_DELEGATION_TOKEN to false

[ https://issues.apache.org/jira/browse/YARN-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630619#comment-13630619 ] Daryn Sharp commented on YARN-503: -- bq. There's likely a race between the RenewalTask and A

[jira] [Commented] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630626#comment-13630626 ] Xuan Gong commented on YARN-561: when container starts as a process, it does not know its co

[jira] [Commented] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630635#comment-13630635 ] Hitesh Shah commented on YARN-561: -- @Xuan, one thing to be careful of this certain env sett

[jira] [Updated] (YARN-412) FifoScheduler incorrectly checking for node locality

[ https://issues.apache.org/jira/browse/YARN-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated YARN-412: --- Fix Version/s: (was: 2.0.4-alpha) 2.0.5-beta > FifoScheduler incorrectly che

[jira] [Commented] (YARN-412) FifoScheduler incorrectly checking for node locality

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

[jira] [Commented] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630652#comment-13630652 ] Xuan Gong commented on YARN-561: Just like ApplicationConstants which include some variables

[jira] [Updated] (YARN-562) NM should reject containers allocated by previous RM

[ https://issues.apache.org/jira/browse/YARN-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-562: - Attachment: YARN-562.1.patch This patch does: 1. add RM's cluster timestamp in NM to reject old containers. 2. Bloc

[jira] [Commented] (YARN-513) Verify all clients will wait for RM to restart

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630672#comment-13630672 ] Xuan Gong commented on YARN-513: >From ApplicationMaster perspective: 1. The very first com

[jira] [Commented] (YARN-513) Verify all clients will wait for RM to restart

[ https://issues.apache.org/jira/browse/YARN-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630677#comment-13630677 ] Bikas Saha commented on YARN-513: - What about other interactions with the RM such as allocat

[jira] [Commented] (YARN-562) NM should reject containers allocated by previous RM

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

[jira] [Commented] (YARN-561) Nodemanager should set some key information into the environment of every container that it launches.

[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630681#comment-13630681 ] Hitesh Shah commented on YARN-561: -- Take a look at ContainerLaunch#sanitizeEnv() and how it

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630734#comment-13630734 ] Sandy Ryza commented on YARN-45: Carlo, I'm glad that this is being proposed. Have you consi

[jira] [Commented] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630741#comment-13630741 ] Omkar Vinit Joshi commented on YARN-547: Canceling the patch as it was fixing the ex

[jira] [Commented] (YARN-503) DelegationTokens will be renewed forever if multiple jobs share tokens and the first one sets JOB_CANCEL_DELEGATION_TOKEN to false

[ https://issues.apache.org/jira/browse/YARN-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630749#comment-13630749 ] Siddharth Seth commented on YARN-503: - bq. I don't like sleeps either. 1s is an eternity

[jira] [Updated] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

[ https://issues.apache.org/jira/browse/YARN-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-547: --- Attachment: yarn-547-20130412.patch > New resource localization is tried even w

[jira] [Updated] (YARN-476) ProcfsBasedProcessTree info message confuses users

[ https://issues.apache.org/jira/browse/YARN-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-476: Attachment: YARN-476.patch > ProcfsBasedProcessTree info message confuses users > ---

[jira] [Commented] (YARN-476) ProcfsBasedProcessTree info message confuses users

[ https://issues.apache.org/jira/browse/YARN-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630759#comment-13630759 ] Sandy Ryza commented on YARN-476: - Attached patch that removes the log statement entirely.

[jira] [Updated] (YARN-476) ProcfsBasedProcessTree info message confuses users

[ https://issues.apache.org/jira/browse/YARN-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-476: Affects Version/s: 2.0.3-alpha > ProcfsBasedProcessTree info message confuses users > ---

[jira] [Updated] (YARN-476) ProcfsBasedProcessTree info message confuses users

[ https://issues.apache.org/jira/browse/YARN-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-476: Priority: Minor (was: Major) > ProcfsBasedProcessTree info message confuses users >

[jira] [Commented] (YARN-547) New resource localization is tried even when Localized Resource is in DOWNLOADING state

s of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12578544/yarn-547-20130412.patch 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-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630769#comment-13630769 ] Bikas Saha commented on YARN-45: I like the idea of the RM giving information to the AM about

[jira] [Commented] (YARN-476) ProcfsBasedProcessTree info message confuses users

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

[jira] [Created] (YARN-573) Shared data structures in Public Localizer and Private Localizer are not Thread safe.

Omkar Vinit Joshi created YARN-573: -- Summary: Shared data structures in Public Localizer and Private Localizer are not Thread safe. Key: YARN-573 URL: https://issues.apache.org/jira/browse/YARN-573 P

[jira] [Created] (YARN-574) PrivateLocalizer does not support parallel resource download via ContainerLocalizer

Omkar Vinit Joshi created YARN-574: -- Summary: PrivateLocalizer does not support parallel resource download via ContainerLocalizer Key: YARN-574 URL: https://issues.apache.org/jira/browse/YARN-574 Pro

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630893#comment-13630893 ] Chris Douglas commented on YARN-45: --- [~sandyr]: Yes, but the correct format/semantics for t

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630898#comment-13630898 ] Carlo Curino commented on YARN-45: -- As you pointed out, any decision made in the RM needs to

[jira] [Created] (YARN-575) ContainerManager APIs should be user accessible

Siddharth Seth created YARN-575: --- Summary: ContainerManager APIs should be user accessible Key: YARN-575 URL: https://issues.apache.org/jira/browse/YARN-575 Project: Hadoop YARN Issue Type: Sub

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630925#comment-13630925 ] Alejandro Abdelnur commented on YARN-45: Comments on the patch. * Reusing ResourceR

[jira] [Commented] (YARN-276) Capacity Scheduler can hang when submit many jobs concurrently

[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630939#comment-13630939 ] nemon lou commented on YARN-276: [~tgraves] Here is the initial thoughts on checking cluster

[jira] [Updated] (YARN-276) Capacity Scheduler can hang when submit many jobs concurrently

[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nemon lou updated YARN-276: --- Attachment: YARN-276.patch uploading a interim patch. > Capacity Scheduler can hang when submi

[jira] [Updated] (YARN-573) Shared data structures in Public Localizer and Private Localizer are not Thread safe.

[ https://issues.apache.org/jira/browse/YARN-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-573: - Issue Type: Sub-task (was: Bug) Parent: YARN-543 > Shared data structu

[jira] [Commented] (YARN-573) Shared data structures in Public Localizer and Private Localizer are not Thread safe.

[ https://issues.apache.org/jira/browse/YARN-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630954#comment-13630954 ] Vinod Kumar Vavilapalli commented on YARN-573: -- So, some of my "TODO: Synchroni

[jira] [Updated] (YARN-574) PrivateLocalizer does not support parallel resource download via ContainerLocalizer

[ https://issues.apache.org/jira/browse/YARN-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-574: - Issue Type: Sub-task (was: Bug) Parent: YARN-543 > PrivateLocalizer do

[jira] [Commented] (YARN-45) Scheduler feedback to AM to release containers

[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630964#comment-13630964 ] Carlo Curino commented on YARN-45: -- [~tucu00] Care to elaborate which properties we don't ca