[jira] [Updated] (YARN-994) HeartBeat thread in AMRMClientAsync does not handle runtime exception correctly

[ https://issues.apache.org/jira/browse/YARN-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-994: --- Attachment: YARN-994.1.patch 1.Heartbeat thread catch throwable instead of IOException and YarnException, and

[jira] [Commented] (YARN-917) Job can fail when RM restarts after staging dir is cleaned but before MR successfully unregister with RM

[ https://issues.apache.org/jira/browse/YARN-917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723891#comment-13723891 ] Jason Lowe commented on YARN-917: - Yes, that's exactly what I was proposing with my first

[jira] [Created] (YARN-996) REST API support for node resource configuration

Junping Du created YARN-996: --- Summary: REST API support for node resource configuration Key: YARN-996 URL: https://issues.apache.org/jira/browse/YARN-996 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-896) Roll up for long lived YARN

[ https://issues.apache.org/jira/browse/YARN-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723968#comment-13723968 ] Siddharth Seth commented on YARN-896: - bq. Robert Joseph Evans Applications may connect

[jira] [Created] (YARN-998) Persistent resource change during NM restart

Junping Du created YARN-998: --- Summary: Persistent resource change during NM restart Key: YARN-998 URL: https://issues.apache.org/jira/browse/YARN-998 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-997) JMX support for node resource configuration

[ https://issues.apache.org/jira/browse/YARN-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723979#comment-13723979 ] Philip Zeyliger commented on YARN-997: -- It seems like having three ways to do the same

[jira] [Commented] (YARN-993) job can not recovery after restart resourcemanager

[ https://issues.apache.org/jira/browse/YARN-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723970#comment-13723970 ] Jason Lowe commented on YARN-993: - This looks more like a MAPREDUCE issue to me. The MR AM

[jira] [Created] (YARN-997) JMX support for node resource configuration

Junping Du created YARN-997: --- Summary: JMX support for node resource configuration Key: YARN-997 URL: https://issues.apache.org/jira/browse/YARN-997 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-988) RM /proxy/app always gives HTML response

[ https://issues.apache.org/jira/browse/YARN-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723984#comment-13723984 ] Srimanth Gunturi commented on YARN-988: --- [~hitesh], My original goal was to get MR2

[jira] [Created] (YARN-1000) Dynamic resource configuration feature can be configured to enable or disable and persistent on setting or not

Junping Du created YARN-1000: Summary: Dynamic resource configuration feature can be configured to enable or disable and persistent on setting or not Key: YARN-1000 URL:

[jira] [Updated] (YARN-996) REST API support for node resource configuration

[ https://issues.apache.org/jira/browse/YARN-996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-996: Description: Besides admin protocol and CLI, REST API should also be supported for node resource

[jira] [Updated] (YARN-1000) Dynamic resource configuration feature can be configured to enable or disable and persistent on setting or not

[ https://issues.apache.org/jira/browse/YARN-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-1000: - Description: There are some configurations for feature of dynamic resource configuration: 1. enable or

[jira] [Created] (YARN-999) In case of long running tasks, reduce node resource should balloon out resource quickly by calling preemption API and suspending running task.

Junping Du created YARN-999: --- Summary: In case of long running tasks, reduce node resource should balloon out resource quickly by calling preemption API and suspending running task. Key: YARN-999 URL:

[jira] [Updated] (YARN-999) In case of long running tasks, reduce node resource should balloon out resource quickly by calling preemption API and suspending running task.

[ https://issues.apache.org/jira/browse/YARN-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-999: Description: In current design and implementation, when we decrease resource on node to less than resource

[jira] [Commented] (YARN-997) JMX support for node resource configuration

[ https://issues.apache.org/jira/browse/YARN-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724022#comment-13724022 ] Junping Du commented on YARN-997: - Hi Philip, thanks for your comments. I saw your comments

[jira] [Commented] (YARN-891) Store completed application information in RM state store

[ https://issues.apache.org/jira/browse/YARN-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724025#comment-13724025 ] Bikas Saha commented on YARN-891: - I would very much like to keep restart storage separate

[jira] [Commented] (YARN-994) HeartBeat thread in AMRMClientAsync does not handle runtime exception correctly

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

[jira] [Commented] (YARN-994) HeartBeat thread in AMRMClientAsync does not handle runtime exception correctly

[ https://issues.apache.org/jira/browse/YARN-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724097#comment-13724097 ] Xuan Gong commented on YARN-994: Test failure is related HeartBeat thread

[jira] [Commented] (YARN-994) HeartBeat thread in AMRMClientAsync does not handle runtime exception correctly

[ https://issues.apache.org/jira/browse/YARN-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724098#comment-13724098 ] Xuan Gong commented on YARN-994: Sorry, test failure is un-related

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724145#comment-13724145 ] Omkar Vinit Joshi commented on YARN-980: [~raghu.hb...@gmail.com] I was looking for

[jira] [Commented] (YARN-589) Expose a REST API for monitoring the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724147#comment-13724147 ] Sandy Ryza commented on YARN-589: - Added a test. Expose a REST API for

[jira] [Updated] (YARN-589) Expose a REST API for monitoring the fair scheduler

[ https://issues.apache.org/jira/browse/YARN-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-589: Attachment: YARN-589-1.patch Expose a REST API for monitoring the fair scheduler

[jira] [Commented] (YARN-925) Read Interface of HistoryStorage for AHS

[ https://issues.apache.org/jira/browse/YARN-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724176#comment-13724176 ] Omkar Vinit Joshi commented on YARN-925: git is not getting synced for some

[jira] [Commented] (YARN-403) Node Manager throws java.io.IOException: Verification of the hashReply failed

[ https://issues.apache.org/jira/browse/YARN-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724186#comment-13724186 ] rohithsharma commented on YARN-403: --- Hash verification is one authentication process at

[jira] [Assigned] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi reassigned YARN-957: -- Assignee: Omkar Vinit Joshi Capacity Scheduler tries to reserve the memory more

[jira] [Commented] (YARN-403) Node Manager throws java.io.IOException: Verification of the hashReply failed

[ https://issues.apache.org/jira/browse/YARN-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724199#comment-13724199 ] Jason Lowe commented on YARN-403: - This sounds like a duplicate of MAPREDUCE-5042 which was

[jira] [Commented] (YARN-953) [YARN-321] Change ResourceManager to use HistoryStorage to log history data

[ https://issues.apache.org/jira/browse/YARN-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724206#comment-13724206 ] Zhijie Shen commented on YARN-953: -- Did some simple test on a single-node cluster as well.

[jira] [Commented] (YARN-961) ContainerManagerImpl should enforce token on server. Today it is [TOKEN, SIMPLE]

[ https://issues.apache.org/jira/browse/YARN-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724215#comment-13724215 ] Vinod Kumar Vavilapalli commented on YARN-961: -- bq. Vinod Kumar Vavilapalli,

[jira] [Commented] (YARN-854) App submission fails on secure deploy

[ https://issues.apache.org/jira/browse/YARN-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724214#comment-13724214 ] Konstantin Shvachko commented on YARN-854: -- Committed to branch 2.0.6.

[jira] [Commented] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724219#comment-13724219 ] Omkar Vinit Joshi commented on YARN-957: attaching a preliminary patch...will add a

[jira] [Updated] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-957: --- Attachment: YARN-957-20130730.1.patch Capacity Scheduler tries to reserve the memory more

[jira] [Commented] (YARN-589) Expose a REST API for monitoring the fair scheduler

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

[jira] [Commented] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724228#comment-13724228 ] Sandy Ryza commented on YARN-957: - I believe we fixed this for the Fair Scheduler in

[jira] [Updated] (YARN-658) Command to kill a YARN application does not work with newer Ubuntu versions

[ https://issues.apache.org/jira/browse/YARN-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Yan updated YARN-658: --- Attachment: yarn-david-nodemanager-david-ubuntu.out yarn-david-resourcemanager-david-ubuntu.out

[jira] [Commented] (YARN-658) Command to kill a YARN application does not work with newer Ubuntu versions

[ https://issues.apache.org/jira/browse/YARN-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724238#comment-13724238 ] David Yan commented on YARN-658: $ uname -a Linux david-ubuntu 3.8.0-27-generic #40-Ubuntu

[jira] [Updated] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghu C Doppalapudi updated YARN-980: - Attachment: (was: NodeManagerlogs.txt) Nodemanager is shutting down while

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724249#comment-13724249 ] Raghu C Doppalapudi commented on YARN-980: -- 2013-07-25 22:46:35,573 INFO

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724246#comment-13724246 ] Raghu C Doppalapudi commented on YARN-980: -- Yeap attached the original log , yes I

[jira] [Updated] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghu C Doppalapudi updated YARN-980: - Attachment: yarn-sfdc-nodemanager.log.23 Nodemanager is shutting down while executing

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724250#comment-13724250 ] Omkar Vinit Joshi commented on YARN-980: yeah it is related to YARN-573... probably

[jira] [Commented] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724251#comment-13724251 ] Omkar Vinit Joshi commented on YARN-980: closing this as duplicate

[jira] [Resolved] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-980. Resolution: Duplicate Nodemanager is shutting down while executing a mapreduce job

[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-tabpanelfocusedCommentId=13724258#comment-13724258 ] Omkar Vinit Joshi commented on YARN-573: Yes this has to be fixed.. It is causing NM

[jira] [Assigned] (YARN-980) Nodemanager is shutting down while executing a mapreduce job

[ https://issues.apache.org/jira/browse/YARN-980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli reassigned YARN-980: Assignee: Omkar Vinit Joshi (was: Vinod Kumar Vavilapalli) Tx for debugging

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

[ https://issues.apache.org/jira/browse/YARN-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724357#comment-13724357 ] Vinod Kumar Vavilapalli commented on YARN-948: -- +1, looks good. Checking this

[jira] [Commented] (YARN-948) RM should validate the release container list before actually releasing them

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

[jira] [Commented] (YARN-988) RM /proxy/app always gives HTML response

[ https://issues.apache.org/jira/browse/YARN-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724403#comment-13724403 ] Hitesh Shah commented on YARN-988: -- The AM is only up while the job is running. Once the

[jira] [Updated] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-643: - Description: The jira is tracking why appToken and clientToAMToken is removed separately, and why they are

[jira] [Commented] (YARN-989) MR2 specific metrics should be collected

[ https://issues.apache.org/jira/browse/YARN-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724437#comment-13724437 ] Hitesh Shah commented on YARN-989: -- What is the use-case that you are trying to solve that

[jira] [Commented] (YARN-985) Nodemanager should log where a resource was localized

[ https://issues.apache.org/jira/browse/YARN-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724507#comment-13724507 ] Jonathan Eagles commented on YARN-985: -- +1. I like the simplicity of this patch and

[jira] [Commented] (YARN-989) MR2 specific metrics should be collected

[ https://issues.apache.org/jira/browse/YARN-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724531#comment-13724531 ] Srimanth Gunturi commented on YARN-989: --- The usecase is to show on Ambari UI the

[jira] [Commented] (YARN-985) Nodemanager should log where a resource was localized

[ https://issues.apache.org/jira/browse/YARN-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724563#comment-13724563 ] Omkar Vinit Joshi commented on YARN-985: [~jeagles] yeah this is a small thing but

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724585#comment-13724585 ] Sandy Ryza commented on YARN-353: - The patch looks good to me, other than the findbugs

[jira] [Commented] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724606#comment-13724606 ] Xuan Gong commented on YARN-643: I think the common place will be BaseFinalTransition.

[jira] [Updated] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

[ https://issues.apache.org/jira/browse/YARN-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-643: --- Attachment: YARN-643.1.patch WHY appToken is removed both in BaseFinalTransition and

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

[ https://issues.apache.org/jira/browse/YARN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724621#comment-13724621 ] Vinod Kumar Vavilapalli commented on YARN-966: -- Looks straight-forward. +1.

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

[ https://issues.apache.org/jira/browse/YARN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724631#comment-13724631 ] Omkar Vinit Joshi commented on YARN-966: few questions.. {code} -assert

[jira] [Updated] (YARN-956) [YARN-321] Add History Store interface and testable in-memory HistoryStorage

[ https://issues.apache.org/jira/browse/YARN-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Bansal updated YARN-956: --- Attachment: YARN-956-2.patch Updating the patch. Thanks, Mayank [YARN-321] Add

[jira] [Commented] (YARN-643) WHY appToken is removed both in BaseFinalTransition and AMUnregisteredTransition AND clientToken is removed in FinalTransition and not BaseFinalTransition

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

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

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

[jira] [Commented] (YARN-956) [YARN-321] Add History Store interface and testable in-memory HistoryStorage

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

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

[ https://issues.apache.org/jira/browse/YARN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724642#comment-13724642 ] Omkar Vinit Joshi commented on YARN-966: * Also I think we are mixing YARN-966 with

[jira] [Resolved] (YARN-939) Rename ContainerManagerImpl to ContainerManagementImpl

[ https://issues.apache.org/jira/browse/YARN-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-939. --- Resolution: Won't Fix Closing this as Won't Fix. Please reopen if required.

[jira] [Resolved] (YARN-992) YARN JMX metrics does not provide information provided in REST calls

[ https://issues.apache.org/jira/browse/YARN-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi resolved YARN-992. --- Resolution: Not A Problem Since the {{root}} queue provides information across the entire

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

[ https://issues.apache.org/jira/browse/YARN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724694#comment-13724694 ] Vinod Kumar Vavilapalli commented on YARN-966: -- bq. after this change are we

[jira] [Commented] (YARN-966) The thread of ContainerLaunch#call will fail without any signal if getLocalizedResources() is called when the container is not at LOCALIZED

[ https://issues.apache.org/jira/browse/YARN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724704#comment-13724704 ] Zhijie Shen commented on YARN-966: -- bq. Also I think we are mixing YARN-966 with YARN-906.

[jira] [Commented] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724741#comment-13724741 ] Omkar Vinit Joshi commented on YARN-957: updating test cases..

[jira] [Updated] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-957: --- Attachment: YARN-957-20130730.2.patch Capacity Scheduler tries to reserve the memory more

[jira] [Updated] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

[ https://issues.apache.org/jira/browse/YARN-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-957: --- Attachment: YARN-957-20130730.3.patch Capacity Scheduler tries to reserve the memory more

[jira] [Commented] (YARN-403) Node Manager throws java.io.IOException: Verification of the hashReply failed

[ https://issues.apache.org/jira/browse/YARN-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724756#comment-13724756 ] Omkar Vinit Joshi commented on YARN-403: yes..it is a duplicate..closing it.

[jira] [Commented] (YARN-291) Dynamic resource configuration

[ https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724758#comment-13724758 ] Junping Du commented on YARN-291: - Hi [~tucu00], as we discussed in Hadoop Summit, I agree

[jira] [Resolved] (YARN-403) Node Manager throws java.io.IOException: Verification of the hashReply failed

[ https://issues.apache.org/jira/browse/YARN-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi resolved YARN-403. Resolution: Duplicate Node Manager throws java.io.IOException: Verification of the

[jira] [Commented] (YARN-957) Capacity Scheduler tries to reserve the memory more than what node manager reports.

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

[jira] [Updated] (YARN-903) DistributedShell throwing Errors in logs after successfull completion

[ https://issues.apache.org/jira/browse/YARN-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omkar Vinit Joshi updated YARN-903: --- Attachment: YARN-903-20130730.1.patch DistributedShell throwing Errors in logs after

[jira] [Commented] (YARN-903) DistributedShell throwing Errors in logs after successfull completion

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

[jira] [Commented] (YARN-903) DistributedShell throwing Errors in logs after successfull completion

[ https://issues.apache.org/jira/browse/YARN-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724785#comment-13724785 ] Omkar Vinit Joshi commented on YARN-903: bq. Not as of now, but potentially in

[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 ] Omkar Vinit Joshi updated YARN-573: --- Attachment: YARN-573-20130730.1.patch Shared data structures in Public Localizer and

[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-tabpanelfocusedCommentId=13724798#comment-13724798 ] Omkar Vinit Joshi commented on YARN-573: can't think of a test case for this..

[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-tabpanelfocusedCommentId=13724807#comment-13724807 ] Hadoop QA commented on YARN-573: {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-602) NodeManager should mandatorily set some Environment variables into every containers that it launches

[ https://issues.apache.org/jira/browse/YARN-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724805#comment-13724805 ] Vinod Kumar Vavilapalli commented on YARN-602: -- [~kj-ki] Can you please update?

[jira] [Updated] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly

[ https://issues.apache.org/jira/browse/YARN-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-107: --- Attachment: YARN-107.2.patch Still throw out KillNonRunningApplicationException when we try to kill the

[jira] [Updated] (YARN-906) Cancelling ContainerLaunch#call at KILLING causes that the container cannot be completed

[ https://issues.apache.org/jira/browse/YARN-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-906: - Attachment: YARN-906.3.patch Thanks Vinod for the hint. In the newer patch, I don't remove the code of

[jira] [Commented] (YARN-107) ClientRMService.forceKillApplication() should handle the non-RUNNING applications properly

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

[jira] [Created] (YARN-1001) YARN should provide per application-type and state statistics

Srimanth Gunturi created YARN-1001: -- Summary: YARN should provide per application-type and state statistics Key: YARN-1001 URL: https://issues.apache.org/jira/browse/YARN-1001 Project: Hadoop YARN

[jira] [Commented] (YARN-906) Cancelling ContainerLaunch#call at KILLING causes that the container cannot be completed

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

[jira] [Resolved] (YARN-988) RM /proxy/app always gives HTML response

[ https://issues.apache.org/jira/browse/YARN-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srimanth Gunturi resolved YARN-988. --- Resolution: Invalid Information provided via YARN-1001 would be sufficient for the intent of