hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-278) Should DFS outputstream's close wait forever?
Date Sun, 12 Jul 2009 01:49:15 GMT

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

dhruba borthakur commented on HDFS-278:

Thanks for the tip Nicholas. I will compile the latest trunk from common and checkin the files
lib/hadoop-core-0.21.0-dev.jar and lib/hadoop-core-test-0.21.0-dev.jar.

> 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
> 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.

View raw message