[jira] [Commented] (YARN-541) getAllocatedContainers() is not returning all the allocated containers

2013-04-15 Thread Krishna Kishore Bonagiri (JIRA)
[ https://issues.apache.org/jira/browse/YARN-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631564#comment-13631564 ] Krishna Kishore Bonagiri commented on YARN-541: --- Hi Hitesh, Thanks for the

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

2013-04-15 Thread nemon lou (JIRA)
[ 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 This patch includes: 1,Checking AM used resources in each leaf queue ,remove

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

2013-04-15 Thread nemon lou (JIRA)
[ 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 Capacity Scheduler can hang when submit many jobs concurrently

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

2013-04-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631585#comment-13631585 ] Hadoop QA commented on YARN-276: {color:red}-1 overall{color}. Here are the results of

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

2013-04-15 Thread nemon lou (JIRA)
[ 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 Capacity Scheduler can hang when submit many jobs concurrently

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

2013-04-15 Thread nemon lou (JIRA)
[ 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 Capacity Scheduler can hang when submit many jobs concurrently

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

2013-04-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631599#comment-13631599 ] Hadoop QA commented on YARN-276: {color:green}+1 overall{color}. Here are the results of

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

2013-04-15 Thread nemon lou (JIRA)
[ 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 Capacity Scheduler can hang when submit many jobs concurrently

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

2013-04-15 Thread Steve Loughran (JIRA)
[ 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.6.patch same source, patch created with a {{git diff trunk..HEAD}} in the hope

[jira] [Resolved] (YARN-20) More information for yarn.resourcemanager.webapp.address in yarn-default.xml

2013-04-15 Thread nemon lou (JIRA)
[ https://issues.apache.org/jira/browse/YARN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nemon lou resolved YARN-20. --- Resolution: Won't Fix More information for yarn.resourcemanager.webapp.address in yarn-default.xml

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

2013-04-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631659#comment-13631659 ] Hadoop QA commented on YARN-276: {color:green}+1 overall{color}. Here are the results of

[jira] [Reopened] (YARN-20) More information for yarn.resourcemanager.webapp.address in yarn-default.xml

2013-04-15 Thread Harsh J (JIRA)
[ https://issues.apache.org/jira/browse/YARN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J reopened YARN-20: - More information for yarn.resourcemanager.webapp.address in yarn-default.xml

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

2013-04-15 Thread Thomas Graves (JIRA)
[ https://issues.apache.org/jira/browse/YARN-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631720#comment-13631720 ] Thomas Graves commented on YARN-276: thanks for the update Nemon. You are going to want

[jira] [Commented] (YARN-445) Ability to signal containers

2013-04-15 Thread Jason Lowe (JIRA)
[ https://issues.apache.org/jira/browse/YARN-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631761#comment-13631761 ] Jason Lowe commented on YARN-445: - Yes, it's an enhancement request to the NM API. I filed

[jira] [Commented] (YARN-501) Application Master getting killed randomly reporting excess usage of memory

2013-04-15 Thread Krishna Kishore Bonagiri (JIRA)
[ https://issues.apache.org/jira/browse/YARN-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631798#comment-13631798 ] Krishna Kishore Bonagiri commented on YARN-501: --- What I have observed today is

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

2013-04-15 Thread Xuan Gong (JIRA)
[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-561: --- Attachment: YARN-561.1.patch 1. add some contant: containerId, nm_host,nm_port to Environment. 2. Add one

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

2013-04-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631903#comment-13631903 ] Hadoop QA commented on YARN-561: {color:green}+1 overall{color}. Here are the results of

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

2013-04-15 Thread Omkar Vinit Joshi (JIRA)
[ 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-20130415.patch Fixing failed test cases. New resource

[jira] [Updated] (YARN-149) ResourceManager (RM) High-Availability (HA)

2013-04-15 Thread Philip Zeyliger (JIRA)
[ https://issues.apache.org/jira/browse/YARN-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Zeyliger updated YARN-149: - Description: One of the goals presented on MAPREDUCE-279 was to have high availability. One way

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Sandy Ryza (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631978#comment-13631978 ] Sandy Ryza commented on YARN-444: - bq. As a logic extension of this, I think we should

[jira] [Updated] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Sandy Ryza (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-444: Attachment: YARN-444-2.patch Move special container exit codes from YarnConfiguration to API

[jira] [Commented] (YARN-549) Asynchronous application submission

2013-04-15 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631990#comment-13631990 ] Zhijie Shen commented on YARN-549: -- After application store is moved out of

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

2013-04-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631994#comment-13631994 ] Hadoop QA commented on YARN-117: {color:red}-1 overall{color}. Here are the results of

[jira] [Assigned] (YARN-553) Have GetNewApplicationResponse generate a directly usable ApplicationSubmissionContext

2013-04-15 Thread Karthik Kambatla (JIRA)
[ https://issues.apache.org/jira/browse/YARN-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-553: - Assignee: Karthik Kambatla Have GetNewApplicationResponse generate a directly usable

[jira] [Reopened] (YARN-77) Test case TestAMRMRPCNodeUpdates.testAMRMUnusableNodes fails occasionally

2013-04-15 Thread Karthik Kambatla (JIRA)
[ https://issues.apache.org/jira/browse/YARN-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reopened YARN-77: -- Assignee: Karthik Kambatla Ran into this again. Taking a look. Test case

[jira] [Commented] (YARN-445) Ability to signal containers

2013-04-15 Thread Chris Nauroth (JIRA)
[ https://issues.apache.org/jira/browse/YARN-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632028#comment-13632028 ] Chris Nauroth commented on YARN-445: Unfortunately, I don't believe the Unix signal

[jira] [Updated] (YARN-482) FS: Extend SchedulingMode to intermediate queues

2013-04-15 Thread Karthik Kambatla (JIRA)
[ https://issues.apache.org/jira/browse/YARN-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-482: -- Attachment: yarn-482.patch Updated the patch to decouple the reserved/ non-reserved cases of

[jira] [Commented] (YARN-98) NM Application invalid state transition on reboot command from RM

2013-04-15 Thread Omkar Vinit Joshi (JIRA)
[ https://issues.apache.org/jira/browse/YARN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632040#comment-13632040 ] Omkar Vinit Joshi commented on YARN-98: --- Earlier this error was present. However now

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632053#comment-13632053 ] Hadoop QA commented on YARN-444: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-482) FS: Extend SchedulingMode to intermediate queues

2013-04-15 Thread Sandy Ryza (JIRA)
[ https://issues.apache.org/jira/browse/YARN-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632054#comment-13632054 ] Sandy Ryza commented on YARN-482: - Karthik, the patch is looking good. A few comments: *

[jira] [Commented] (YARN-358) bundle container classpath in temporary jar on all platforms, not just Windows

2013-04-15 Thread Chris Nauroth (JIRA)
[ https://issues.apache.org/jira/browse/YARN-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632068#comment-13632068 ] Chris Nauroth commented on YARN-358: {quote} @Chris, are we just talking about the

[jira] [Updated] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Sandy Ryza (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-444: Attachment: YARN-444-2.patch Move special container exit codes from YarnConfiguration to API

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Sandy Ryza (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632080#comment-13632080 ] Sandy Ryza commented on YARN-444: - Sorry, had a stale version of trunk. Latest patch should

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

2013-04-15 Thread Bikas Saha (JIRA)
[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632081#comment-13632081 ] Bikas Saha commented on YARN-514: - If we are going to change the enum values then we might

[jira] [Resolved] (YARN-98) NM Application invalid state transition on reboot command from RM

2013-04-15 Thread Omkar Vinit Joshi (JIRA)
[ https://issues.apache.org/jira/browse/YARN-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-98. --- Resolution: Duplicate After yarn-495 fix this issue is not reproducible. Closing it as a

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632130#comment-13632130 ] Hadoop QA commented on YARN-444: {color:green}+1 overall{color}. Here are the results of

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

2013-04-15 Thread Omkar Vinit Joshi (JIRA)
[ https://issues.apache.org/jira/browse/YARN-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632146#comment-13632146 ] Omkar Vinit Joshi commented on YARN-573: We need to fix one more problem present in

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Vinod Kumar Vavilapalli (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632147#comment-13632147 ] Vinod Kumar Vavilapalli commented on YARN-444: -- This looks good, checking it

[jira] [Commented] (YARN-445) Ability to signal containers

2013-04-15 Thread Bikas Saha (JIRA)
[ https://issues.apache.org/jira/browse/YARN-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632178#comment-13632178 ] Bikas Saha commented on YARN-445: - IMO it would be great if the API allows YARN/NM to figure

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

2013-04-15 Thread Zhijie Shen (JIRA)
[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-514: - Attachment: YARN-514.5.patch I've drafted a newer patch, where YarnApplicationState,

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

2013-04-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632248#comment-13632248 ] Hadoop QA commented on YARN-514: {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (YARN-482) FS: Extend SchedulingMode to intermediate queues

2013-04-15 Thread Karthik Kambatla (JIRA)
[ https://issues.apache.org/jira/browse/YARN-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-482: -- Attachment: yarn-482.patch Thanks Sandy. Here is a patch that addresses almost all your

[jira] [Commented] (YARN-482) FS: Extend SchedulingMode to intermediate queues

2013-04-15 Thread Sandy Ryza (JIRA)
[ https://issues.apache.org/jira/browse/YARN-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632287#comment-13632287 ] Sandy Ryza commented on YARN-482: - Thanks Karthik. The latest patch looks good to me.

[jira] [Updated] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Sandy Ryza (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-444: Attachment: YARN-444-2.patch Move special container exit codes from YarnConfiguration to API

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Sandy Ryza (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632322#comment-13632322 ] Sandy Ryza commented on YARN-444: - Thanks Vinod. Uploaded a patch that applies cleanly on

[jira] [Created] (YARN-577) ApplicationReport does not provide progress value of application

2013-04-15 Thread Hitesh Shah (JIRA)
Hitesh Shah created YARN-577: Summary: ApplicationReport does not provide progress value of application Key: YARN-577 URL: https://issues.apache.org/jira/browse/YARN-577 Project: Hadoop YARN

[jira] [Updated] (YARN-577) ApplicationReport does not provide progress value of application

2013-04-15 Thread Hitesh Shah (JIRA)
[ https://issues.apache.org/jira/browse/YARN-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-577: - Assignee: Vinod Kumar Vavilapalli ApplicationReport does not provide progress value of application

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632353#comment-13632353 ] Hadoop QA commented on YARN-444: {color:green}+1 overall{color}. Here are the results of

[jira] [Commented] (YARN-577) ApplicationReport does not provide progress value of application

2013-04-15 Thread Karthik Kambatla (JIRA)
[ https://issues.apache.org/jira/browse/YARN-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632358#comment-13632358 ] Karthik Kambatla commented on YARN-577: --- Good idea.

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

2013-04-15 Thread Vinod Kumar Vavilapalli (JIRA)
[ https://issues.apache.org/jira/browse/YARN-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-570: Assignee: PengZhang Time strings are formated in different timezone

[jira] [Updated] (YARN-547) Race condition in Public Localizer may result into resource getting downloaded again

2013-04-15 Thread Omkar Vinit Joshi (JIRA)
, yarn-547-20130412.patch, yarn-547-20130415.patch At present when multiple containers try to request a localized resource 1) If the resource is not present then first it is created and Resource Localization starts ( LocalizedResource is in DOWNLOADING state) 2) Now if in this state multiple

[jira] [Commented] (YARN-444) Move special container exit codes from YarnConfiguration to API

2013-04-15 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/YARN-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632402#comment-13632402 ] Hudson commented on YARN-444: - Integrated in Hadoop-trunk-Commit #3615 (See

[jira] [Commented] (YARN-77) Test case TestAMRMRPCNodeUpdates.testAMRMUnusableNodes fails occasionally

2013-04-15 Thread Karthik Kambatla (JIRA)
[ https://issues.apache.org/jira/browse/YARN-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632413#comment-13632413 ] Karthik Kambatla commented on YARN-77: -- In DrainDispatcher#getEventHandler(), drained is

[jira] [Commented] (YARN-77) Test case TestAMRMRPCNodeUpdates.testAMRMUnusableNodes fails occasionally

2013-04-15 Thread Karthik Kambatla (JIRA)
[ https://issues.apache.org/jira/browse/YARN-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632415#comment-13632415 ] Karthik Kambatla commented on YARN-77: -- [~vinodkv], do you remember why {{drained}} is

[jira] [Updated] (YARN-547) Race condition in Public Localizer may result into resource getting downloaded again

2013-04-15 Thread Omkar Vinit Joshi (JIRA)
Issue Type: Sub-task Reporter: Omkar Vinit Joshi Assignee: Omkar Vinit Joshi Attachments: yarn-547-20130411.1.patch, yarn-547-20130411.patch, yarn-547-20130412.patch, yarn-547-20130415.patch At present when multiple containers try to request

[jira] [Updated] (YARN-547) Race condition in Public / Private Localizer may result into resource getting downloaded again

2013-04-15 Thread Omkar Vinit Joshi (JIRA)
, yarn-547-20130411.patch, yarn-547-20130412.patch, yarn-547-20130415.patch At present when multiple containers try to request a localized resource * If the resource is not present then first it is created and Resource Localization starts ( LocalizedResource is in DOWNLOADING state) * Now

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

2013-04-15 Thread Jian He (JIRA)
[ 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.2.patch Add a timeStamp field in Container to indicate when was container allocated, let NM

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

2013-04-15 Thread Carlo Curino (JIRA)
[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632511#comment-13632511 ] Carlo Curino commented on YARN-45: -- [~bikassaha] Sounds good, I totally agree with the

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

2013-04-15 Thread Alejandro Abdelnur (JIRA)
[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632531#comment-13632531 ] Alejandro Abdelnur commented on YARN-45: Got it, makes sense.

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

2013-04-15 Thread Bikas Saha (JIRA)
[ https://issues.apache.org/jira/browse/YARN-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632536#comment-13632536 ] Bikas Saha commented on YARN-514: - Sorry for not catching this earlier.

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

2013-04-15 Thread Bikas Saha (JIRA)
[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632542#comment-13632542 ] Bikas Saha commented on YARN-45: I took a quick look at this patch and the others and from

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

2013-04-15 Thread Arun C Murthy (JIRA)
[ https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13632571#comment-13632571 ] Arun C Murthy commented on YARN-45: --- Sorry, I've been away for a couple of weeks due to

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

2013-04-15 Thread Vinod Kumar Vavilapalli (JIRA)
[ https://issues.apache.org/jira/browse/YARN-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-571: - Attachment: YARN-571-20130415.2.txt Here's a patch that fixes this: - Moved user

[jira] [Moved] (YARN-578) NodeManager should use SecureIOUtils for serving logs and intermediate outputs

2013-04-15 Thread Vinod Kumar Vavilapalli (JIRA)
[ https://issues.apache.org/jira/browse/YARN-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli moved MAPREDUCE-3731 to YARN-578: - Component/s: (was: security)

[jira] [Updated] (YARN-578) NodeManager should use SecureIOUtils for serving logs and intermediate outputs

2013-04-15 Thread Vinod Kumar Vavilapalli (JIRA)
[ https://issues.apache.org/jira/browse/YARN-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-578: - Issue Type: Sub-task (was: Bug) Parent: YARN-47 NodeManager should

[jira] [Updated] (YARN-579) Make ApplicationToken part of Container's token list to help RM-restart

2013-04-15 Thread Vinod Kumar Vavilapalli (JIRA)
[ https://issues.apache.org/jira/browse/YARN-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-579: - Summary: Make ApplicationToken part of Container's token list to help RM-restart

[jira] [Created] (YARN-579) Make ApplicationToken part of Container's token list to help restart

2013-04-15 Thread Vinod Kumar Vavilapalli (JIRA)
Vinod Kumar Vavilapalli created YARN-579: Summary: Make ApplicationToken part of Container's token list to help restart Key: YARN-579 URL: https://issues.apache.org/jira/browse/YARN-579