You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2007/01/17 00:21:27 UTC
[jira] Commented: (HADOOP-762) "Bad File Descriptor" in closing
local file
[ https://issues.apache.org/jira/browse/HADOOP-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465326 ]
Raghu Angadi commented on HADOOP-762:
-------------------------------------
We will need a fix similar to one in HADOOP-758, where exceptions during try{} blocks are reported and exceptions in finally {} are ignored. HADOOP-757 fixes this perticular 'bad file descriptor' exception.
> "Bad File Descriptor" in closing local file
> -------------------------------------------
>
> Key: HADOOP-762
> URL: https://issues.apache.org/jira/browse/HADOOP-762
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.8.0
> Reporter: Nigel Daley
> Assigned To: Owen O'Malley
>
> Running the sort benchmark, I had a map fail with this exception:
> 2006-11-28 17:59:36,770 INFO org.apache.hadoop.mapred.TaskInProgress: Error from task_0001_m_001906_0: Map output lost, rescheduling: getMapOutput(task_0001_m_001906_0,786) failed :
> java.io.IOException: Bad file descriptor
> at java.io.FileInputStream.close0(Native Method)
> at java.io.FileInputStream.close(FileInputStream.java:245)
> at org.apache.hadoop.fs.LocalFileSystem$LocalFSFileInputStream.close(LocalFileSystem.java:100)
> at java.io.FilterInputStream.close(FilterInputStream.java:159)
> at org.apache.hadoop.fs.FSDataInputStream$Checker.close(FSDataInputStream.java:162)
> at java.io.FilterInputStream.close(FilterInputStream.java:159)
> at java.io.BufferedInputStream.close(BufferedInputStream.java:440)
> at java.io.FilterInputStream.close(FilterInputStream.java:159)
> at org.apache.hadoop.mapred.TaskTracker$MapOutputServlet.doGet(TaskTracker.java:1446)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427)
> at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:475)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
> at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:635)
> at org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
> at org.mortbay.http.HttpServer.service(HttpServer.java:954)
> at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
> at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
> at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
> at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
> at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
> at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira