hadoop-mapreduce-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MAPREDUCE-8) "Bad File Descriptor" in closing local file
Date Sat, 31 Dec 2011 08:48:31 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Harsh J resolved MAPREDUCE-8.
-----------------------------

    Resolution: Not A Problem

Not a problem anymore. HADOOP-757 apparently fixed it a long time ago.
                
> "Bad File Descriptor" in closing local file
> -------------------------------------------
>
>                 Key: MAPREDUCE-8
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-8
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Nigel Daley
>            Assignee: 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, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message