hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J Chouraria (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1603) Namenode gets sticky if one of namenode storage volumes disappears (removed, unmounted, etc.)
Date Wed, 01 Jun 2011 05:45:47 GMT

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

Harsh J Chouraria commented on HDFS-1603:

I've noticed a failure during an unlock call that occurs AFTER a SD has been detected as a
failed point. The unlock call went ahead and blocked via a native call to the NFS lock daemon
- and since the NFS server was down, it just hung (odd that the timeout did not apply, probably
an nfs lockd issue, but I do not feel its OK to unlock after a directory has caused a processIOError

> Namenode gets sticky if one of namenode storage volumes disappears (removed, unmounted,
> ---------------------------------------------------------------------------------------------
>                 Key: HDFS-1603
>                 URL: https://issues.apache.org/jira/browse/HDFS-1603
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.21.0
>            Reporter: Konstantin Boudnik
> While investigating failures on HDFS-1602 it became apparent that once a namenode storage
volume is pulled out NN becomes completely "sticky" until {{FSImage:processIOError: removing
storage}} move the storage from the active set. During this time none of normal NN operations
are possible (e.g. creating a directory on HDFS timeouts eventually).
> In case of NFS this can be workaround'd with soft,intr,timeo,retrans settings. However,
a better handling of the situation is apparently possible and needs to be implemented.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message