[
https://issues.apache.org/jira/browse/HADOOP-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797429#action_12797429
]
Konstantin Boudnik commented on HADOOP-4963:
--------------------------------------------
I've merged it back to the branch 0.19. CHANGES.txt file has been updated to
reflect that this fix was integrated into unrelease 0.19.3 This release
actually doesn't exist, so it needs to be created within the JIRA system.
> 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 Common
> Issue Type: Bug
> Affects Versions: 0.19.0, 0.20.0
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Minor
> Fix For: 0.20.0
>
> Attachments: patch-4963.txt, 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.
