[ https://issues.apache.org/jira/browse/HADOOP-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676423#action_12676423 ]
Hairong Kuang commented on HADOOP-3998: --------------------------------------- If the datanode is really dead, the client should not get RemoteException. The question is if there are cases that require retry when a client receives RemoteException. One correction: the jira that I referred to in previous comments should be HADOOP-5311. Dhruba, would it be better to discuss lease recovery at HADOOP-5311? This jira seems to be about client close order. > Got an exception from ClientFinalizer when the JT is terminated > --------------------------------------------------------------- > > Key: HADOOP-3998 > URL: https://issues.apache.org/jira/browse/HADOOP-3998 > Project: Hadoop Core > Issue Type: Bug > Components: dfs > Affects Versions: 0.19.0 > Reporter: Amar Kamat > Assignee: dhruba borthakur > Fix For: 0.19.2 > > Attachments: closeAll.patch, closeAll.patch > > > This happens when we terminate the JT using _control-C_. It throws the > following exception > {noformat} > Exception closing file my-file > java.io.IOException: Filesystem closed > at org.apache.hadoop.hdfs.DFSClient.checkOpen(DFSClient.java:193) > at org.apache.hadoop.hdfs.DFSClient.access$700(DFSClient.java:64) > at > org.apache.hadoop.hdfs.DFSClient$DFSOutputStream.closeInternal(DFSClient.java:2868) > at > org.apache.hadoop.hdfs.DFSClient$DFSOutputStream.close(DFSClient.java:2837) > at > org.apache.hadoop.hdfs.DFSClient$LeaseChecker.close(DFSClient.java:808) > at org.apache.hadoop.hdfs.DFSClient.close(DFSClient.java:205) > at > org.apache.hadoop.hdfs.DistributedFileSystem.close(DistributedFileSystem.java:253) > at > org.apache.hadoop.fs.FileSystem$Cache.closeAll(FileSystem.java:1367) > at org.apache.hadoop.fs.FileSystem.closeAll(FileSystem.java:234) > at > org.apache.hadoop.fs.FileSystem$ClientFinalizer.run(FileSystem.java:219) > {noformat} > Note that _my-file_ is some file used by the JT. > Also if there is some file renaming done, then the exception states that the > earlier file does not exist. I am not sure if this is a MR issue or a DFS > issue. Opening this issue for investigation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.