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 "Ravi Gummadi (JIRA)" <ji...@apache.org> on 2009/03/20 12:46:51 UTC

[jira] Commented: (HADOOP-5537) Tasklog servlet doesn't display any logs when logs are short

    [ https://issues.apache.org/jira/browse/HADOOP-5537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683852#action_12683852 ] 

Ravi Gummadi commented on HADOOP-5537:
--------------------------------------

We are planning to address this issue as part of HADOOP-4374.

> Tasklog servlet doesn't display any logs when logs are short
> ------------------------------------------------------------
>
>                 Key: HADOOP-5537
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5537
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>            Reporter: Michael Bieniosek
>
> After running a job that died after only writing a little bit of logs, the tasklog servlet shows an empty log.  In the log directory, however, there are non-empty stderr and stdout logs:
> $ ls -la
> total 92
> drwxrwsr-x  2 mapreduce mapreduce  4096 Mar 19 16:24 .
> drwxrwsr-x 95 mapreduce mapreduce 69632 Mar 19 16:24 ..
> -rw-r--r--  1 mapreduce mapreduce    78 Mar 19 16:24 log.index
> -rw-rw-r--  1 mapreduce mapreduce   350 Mar 19 16:24 stderr
> -rw-rw-r--  1 mapreduce mapreduce  4413 Mar 19 16:24 stdout
> $ cat log.index 
> LOG_DIR:attempt_200902160142_0040_m_000000_3
> stdout:0 0
> stderr:0 0
> syslog:0 0

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