hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5500) Critical datanode threads may terminate silently on uncaught exceptions
Date Thu, 12 May 2016 22:22:13 GMT

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

Sangjin Lee commented on HDFS-5500:

There has been no movement on this for a while. We'll need to move it out of scope for 2.8.0
soon. Let me know if you disagree.

> Critical datanode threads may terminate silently on uncaught exceptions
> -----------------------------------------------------------------------
>                 Key: HDFS-5500
>                 URL: https://issues.apache.org/jira/browse/HDFS-5500
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Kihwal Lee
>            Priority: Critical
> We've seen refreshUsed (DU) thread disappearing on uncaught exceptions. This can go unnoticed
for a long time.  If OOM occurs, more things can go wrong.  On one occasion, Timer, multiple
refreshUsed and DataXceiverServer thread had terminated.  
> DataXceiverServer catches OutOfMemoryError and sleeps for 30 seconds, but I am not sure
it is really helpful. In once case, the thread did it multiple times then terminated. I suspect
another OOM was thrown while in a catch block.  As a result, the server socket was not closed
and clients hung on connect. If it had at least closed the socket, client-side would have
been impacted less.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message