Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <584857953.1247419514826.JavaMail.jira@brutus>
Date: Sun, 12 Jul 2009 10:25:14 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-278) Should DFS outputstream's close wait
 forever?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

dhruba borthakur commented on HDFS-278:
---------------------------------------

All unit tests passed except TestHDFSCLI and TestNNThroughputBenchmark. 

> Should DFS outputstream's close wait forever?
> ---------------------------------------------
>
>                 Key: HDFS-278
>                 URL: https://issues.apache.org/jira/browse/HDFS-278
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Raghu Angadi
>            Assignee: dhruba borthakur
>             Fix For: 0.21.0
>
>         Attachments: softMount1.patch, softMount1.patch, softMount2.patch, softMount3.patch, softMount4.txt, softMount5.txt, softMount6.txt, softMount7.txt, softMount8.txt, softMount9.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.