[ https://issues.apache.org/jira/browse/HDFS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HDFS-278: ---------------------------------- Status: Open (was: Patch Available) Re-triggring HudsonQA > 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 > 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.