You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2009/04/16 01:27:14 UTC

[jira] Commented: (HADOOP-2757) Should DFS outputstream's close wait forever?

    [ https://issues.apache.org/jira/browse/HADOOP-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699447#action_12699447 ] 

dhruba borthakur commented on HADOOP-2757:
------------------------------------------

I would like to provide a test case that demonstrates this behaviour. And also a fix that makes amy dfsclient methods return error if the dfsclient was unable to communicate with the dfs servers for a configured period of time. 

In the current implementation, the dfs client is like a nfs hard-mount. It hangs when the servers die. This is a problem for most long-running applications that use hdfs to store data. I would implement an option that will make the dfs client behave like a soft nfs mount..

> Should DFS outputstream's close wait forever?
> ---------------------------------------------
>
>                 Key: HADOOP-2757
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2757
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Raghu Angadi
>            Assignee: dhruba borthakur
>
> Currently {{DFSOutputStream.close()}} waits for ever if Namenode keeps throwing {{NotYetReplicated}} exception, for whatever reason. Its pretty annoying for a user. Shoud the loop inside close have a timeout? If so how much? It could probably something like 10 minutes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.