hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Trivial Update of "WritingYarnApps" by HiteshShah
Date Thu, 03 Nov 2011 23:34:48 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "WritingYarnApps" page has been changed by HiteshShah:
http://wiki.apache.org/hadoop/WritingYarnApps?action=diff&rev1=17&rev2=18

  
    This is likely due to high memory usage exceeding your requested container memory size.
There are a number of reasons that can cause this. First, look at the process tree that the
node manager dumps when it kills your container.  The two things you're interested in are
physical memory and virtual memory.  If you have exceeded physical memory limits your app
is using too much physical memory. If you're running a Java app, you can use -hprof to look
at what is taking up space in the heap. If you have exceeded virtual memory, things are slightly
more complicated.
  
+ == How can my ApplicationMaster kill a container? Releasing it via AMRMProtocol#allocate
does not seem to work. ==
+ 
+   A container can only be released back to the ResourceManager if it has not been launched.
To kill a launched container, the ApplicationMaster can send a stop command to the container
via ContainerManager#stopContainer(StopContainerRequest request). This will trigger a kill
event to the launched container and this container will eventually be part of the list of
completed Containers in the RM's response to the AM on an AMRMProtocol#allocate call. 
+ 
  =  Useful Links =
  
    * [[https://issues.apache.org/jira/secure/attachment/12486023/MapReduce_NextGen_Architecture.pdf|Map
Reduce Next Generation Architecture]]

Mime
View raw message