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

["dhruba borthakur (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dhruba borthakur updated HADOOP-2757:
-------------------------------------

    Attachment: softMount4.txt

1. Introduced a new boolean configurable variable called ipc.client.ping that specifies whether the rpc client is supposed to send a periodic ping or not.
2. A dfs writer bails out if the renewLease() fails once
3. DFSOutputStream.close() retries the close call as long as it is within the time specified by ipc.ping.interval.

> 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
>         Attachments: softMount1.patch, softMount1.patch, softMount2.patch, softMount3.patch, softMount4.txt
>
>
> 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.