[
https://issues.apache.org/jira/browse/HADOOP-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670924#action_12670924
]
Stefan Will commented on HADOOP-3998:
-------------------------------------
I'm seeing the same kind of error when I hit Ctrl-C to kill a client, but also
occasionally in tasks that write out sideband data via MultipleOutputs.java.
The ClientFinalizer is called as a Shutdown hook, and my suspicion is that it's
some kind of race condition with perhaps the filesystem finalizer or some other
method that is responsible for closing the filesystem.
I'm running the following JVM:
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) 64-Bit Server VM (build 11.0-b15, mixed mode)
On CentOS 5.
> 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
>
> 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.
