You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/17 19:09:05 UTC

[jira] [Resolved] (MAPREDUCE-417) Logging could hang/fail when drive is filled by mapred outputs.

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

Allen Wittenauer resolved MAPREDUCE-417.
----------------------------------------

    Resolution: Fixed

I'm going to mark this as fixed due to how user logging is now handled.

> Logging could hang/fail when drive is filled by mapred outputs.
> ---------------------------------------------------------------
>
>                 Key: MAPREDUCE-417
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-417
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Koji Noguchi
>            Priority: Minor
>
> HADOOP-1252 addresses the mapred disk problems.
> In addition to those problems, if mapred fills up the drive used for logging, it might affect TaskTracker/DataNodes.
> Simple solution for now is not to use the logging drive in MapReduce. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)