hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Zeyliger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7283) Bump DataNode OOM log from WARN to ERROR
Date Thu, 23 Oct 2014 20:46:34 GMT

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

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

Changing the log message to ERROR sounds like a great idea.  I've taken, however, to running
my datanodes so that they die completely on OutOfMemory because depending on where the exception
happens, some things can't recover.

> 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)

Mime
View raw message