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 "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2009/01/06 07:17:44 UTC
[jira] Commented: (HADOOP-4963) Logs saying
org.apache.hadoop.util.DiskChecker$DiskErrorException in TaskTracker are
not relevant
[ https://issues.apache.org/jira/browse/HADOOP-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661055#action_12661055 ]
Amareshwari Sriramadasu commented on HADOOP-4963:
-------------------------------------------------
test-patch and ant test passed
> Logs saying org.apache.hadoop.util.DiskChecker$DiskErrorException in TaskTracker are not relevant
> -------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4963
> URL: https://issues.apache.org/jira/browse/HADOOP-4963
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: patch-4963.txt
>
>
> TaskTracker logs has not much relevant logs at info level for
> org.apache.hadoop.util.DiskChecker$DiskErrorException: Could not find taskTracker/jobcache/job_200812311029_0001/attempt_200812311029_0001_m_000000_0/output/file.out in any of the configured local directories.
> This happens when the map has not created output file.
> These logs make it hard to debug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.