You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Philip Zeyliger (JIRA)" <ji...@apache.org> on 2014/10/23 22:09:33 UTC

[jira] [Commented] (HDFS-7283) Bump DataNode OOM log from WARN to ERROR

    [ https://issues.apache.org/jira/browse/HDFS-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181865#comment-14181865 ] 

Philip Zeyliger commented on HDFS-7283:
---------------------------------------

Do we know how this behaves when you use an
{code}
-XX:OnOutOfMemoryError=/some/kill/command
{code}
Java option?

> Bump DataNode OOM log from WARN to ERROR
> ----------------------------------------
>
>                 Key: HDFS-7283
>                 URL: https://issues.apache.org/jira/browse/HDFS-7283
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 2.0.0-alpha
>            Reporter: Stephen Chu
>            Assignee: Stephen Chu
>            Priority: Trivial
>              Labels: supportability
>
> When the DataNode OOMs, it logs the following WARN message which should be bumped up to ERROR because DataNode OOM often leads to DN process abortion.
> {code}
> WARN org.apache.hadoop.hdfs.server.datanode.DataNode: DataNode is out of memory. Will retry in 30 seconds. 
> 4751 java.lang.OutOfMemoryError: unable to create new native thread"
> {code}
> Thanks to Roland Teague for identifying this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)