java.lang.Exception

java.io.IOException: No such file or directory

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1733

  • via Google Groups by Basith Zainurrohman, 6 months ago
    java.io.IOException: No such file or directory
  • "java.io.IOException: No such file or directory"
  • via Google Groups by George Hant, 1 year ago
    java.io.IOException: No such file or directory
  • Stack trace

    • java.lang.Exception: java.io.IOException: No such file or directory at org.apache.hadoop.mapred.LocalJobRunner$Job.runTasks(LocalJobRunner.java:489)[hadoop-mapreduce-client-common-2.6.0-cdh5.8.0.jar:?] at org.apache.hadoop.mapred.LocalJobRunner$Job.run(LocalJobRunner.java:556)[hadoop-mapreduce-client-common-2.6.0-cdh5.8.0.jar:?] Caused by: java.io.IOException: No such file or directory at java.io.UnixFileSystem.createFileExclusively(Native Method)[?:1.7.0_67] at java.io.File.createNewFile(File.java:1006)[?:1.7.0_67] at java.io.File.createTempFile(File.java:1989)[?:1.7.0_67] at java.io.File.createTempFile(File.java:2040)[?:1.7.0_67] at io.druid.indexer.IndexGeneratorJob$IndexGeneratorReducer.reduce(IndexGeneratorJob.java:558)[druid-indexing-hadoop-0.9.1.1.jar:0.9.1.1] at io.druid.indexer.IndexGeneratorJob$IndexGeneratorReducer.reduce(IndexGeneratorJob.java:469)[druid-indexing-hadoop-0.9.1.1.jar:0.9.1.1] at org.apache.hadoop.mapreduce.Reducer.run(Reducer.java:171)[hadoop-mapreduce-client-core-2.6.0-cdh5.8.0.jar:?] at org.apache.hadoop.mapred.ReduceTask.runNewReducer(ReduceTask.java:627)[hadoop-mapreduce-client-core-2.6.0-cdh5.8.0.jar:?] at org.apache.hadoop.mapred.ReduceTask.run(ReduceTask.java:389)[hadoop-mapreduce-client-core-2.6.0-cdh5.8.0.jar:?] at org.apache.hadoop.mapred.LocalJobRunner$Job$ReduceTaskRunnable.run(LocalJobRunner.java:346)[hadoop-mapreduce-client-common-2.6.0-cdh5.8.0.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[?:1.7.0_67] at java.util.concurrent.FutureTask.run(FutureTask.java:262)[?:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[?:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[?:1.7.0_67] at java.lang.Thread.run(Thread.java:745)[?:1.7.0_67]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Once, 6 months ago
    2 times, 7 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    2 times, 2 years ago
    38 more bugmates