[
https://issues.apache.org/jira/browse/HADOOP-5194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672257#action_12672257
]
Vinod K V commented on HADOOP-5194:
-----------------------------------
bq. Hudson also hit this. See
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3820/console
This must be different and may not even refer to a bug. Will look into that
separately.
As for the original report of task and job failures on Cygwin, there seem to be
multiple problems here. The exception that Nicholas reported is appearing on
trunk pre HADOOP-4759. After HADOOP-4759 however, that exception is gone
because of the changes involved in that issue, though tasks still continue to
fail with a "kill unknown jvm" problem.
{code}
09/02/10 18:32:44 INFO mapred.TaskTracker: LaunchTaskAction (registerTask):
attempt_200902101830_0001_m_000003_0 task's state:UNASSIGNED
09/02/10 18:32:44 INFO mapred.TaskTracker: Trying to launch :
attempt_200902101830_0001_m_000003_0
09/02/10 18:32:44 INFO mapred.TaskTracker: In TaskLauncher, current free slots
: 2 and trying to launch attempt_200902101830_0001_m_000003_0
09/02/10 18:32:45 INFO mapred.JvmManager: In JvmRunner constructed JVM ID:
jvm_200902101830_0001_m_1163115666
09/02/10 18:32:45 INFO mapred.JvmManager: JVM Runner
jvm_200902101830_0001_m_1163115666 spawned.
09/02/10 18:32:45 INFO mapred.JvmManager: JVM :
jvm_200902101830_0001_m_1163115666 exited. Number of tasks it ran: 0
09/02/10 18:32:46 INFO mapred.TaskTracker: Killing unknown JVM
jvm_200902101830_0001_m_1163115666
09/02/10 18:32:48 INFO mapred.TaskRunner: attempt_200902101830_0001_m_000003_0
done; removing files.
{code}
> DiskErrorException in TaskTracker when running a job
> ----------------------------------------------------
>
> Key: HADOOP-5194
> URL: https://issues.apache.org/jira/browse/HADOOP-5194
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Environment: Hudson (Solaris?), Windows, Cygwin
> Reporter: Tsz Wo (Nicholas), SZE
> Priority: Blocker
> Fix For: 0.21.0
>
>
> In particular, this can be reproduced in Windows by running a hadoop example
> such as PiEstimator.
> {noformat}
> org.apache.hadoop.util.DiskChecker$DiskErrorException: Could not find
> taskTracker/pids/attempt_200902021632_0001_m_000002_0 in any of the
> configured local directories
> at
> org.apache.hadoop.fs.LocalDirAllocator$AllocatorPerContext.getLocalPathToRead(LocalDirAllocator.java:381)
> at
> org.apache.hadoop.fs.LocalDirAllocator.getLocalPathToRead(LocalDirAllocator.java:138)
> at
> org.apache.hadoop.mapred.TaskTracker.getPidFilePath(TaskTracker.java:430)
> at
> org.apache.hadoop.mapred.TaskTracker.removePidFile(TaskTracker.java:440)
> at
> org.apache.hadoop.mapred.JvmManager$JvmManagerForType$JvmRunner.runChild(JvmManager.java:370)
> at
> org.apache.hadoop.mapred.JvmManager$JvmManagerForType$JvmRunner.run(JvmManager.java:338)
> {noformat}
> (Have changed TaskTracker.java to print out the trace.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
