hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod K V (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (HADOOP-4963) Logs saying org.apache.hadoop.util.DiskChecker$DiskErrorException in TaskTracker are not relevant
Date Thu, 19 Feb 2009 12:54:02 GMT

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

Vinod K V reopened HADOOP-4963:
-------------------------------


Can we get a fix for 0.20 as well? I am seeing a lot of these log messages which are garbling
up the logs and are quite misleading while debugging other issues.

> 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.


Mime
View raw message