You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Robert Chansler (JIRA)" <ji...@apache.org> on 2009/10/09 19:41:31 UTC

[jira] Updated: (HADOOP-5194) DiskErrorException in TaskTracker when running a job

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

Robert Chansler updated HADOOP-5194:
------------------------------------

     Description: 
 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 patch disables usage of setsid and pidfiles on Windows.


  was:
 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.)


    Release Note:   (was: This patch disables usage of setsid and pidfiles on Windows.)

Editorial pass over all release notes prior to publication of 0.21.

> DiskErrorException in TaskTracker when running a job
> ----------------------------------------------------
>
>                 Key: HADOOP-5194
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5194
>             Project: Hadoop Common
>          Issue Type: Bug
>         Environment: Windows, Cygwin
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Ravi Gummadi
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-5194.patch, HADOOP-5194.v1.patch
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
>  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 patch disables usage of setsid and pidfiles on Windows.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.