You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Alok Singh (JIRA)" <ji...@apache.org> on 2010/03/20 05:12:27 UTC
[jira] Commented: (HADOOP-6651) Hadoop should provide a simplified
way of fetching user-logs
[ https://issues.apache.org/jira/browse/HADOOP-6651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847708#action_12847708 ]
Alok Singh commented on HADOOP-6651:
------------------------------------
With the 0.20S comming , there would be some impacts the way user will download the
logs. Probably will use the standard kerboros mechanisms.
> Hadoop should provide a simplified way of fetching user-logs
> ------------------------------------------------------------
>
> Key: HADOOP-6651
> URL: https://issues.apache.org/jira/browse/HADOOP-6651
> Project: Hadoop Common
> Issue Type: New Feature
> Affects Versions: 0.20.0, 0.20.1, 0.20.2
> Reporter: Alok Singh
>
> Hi,
> Currently , in both streaming and normal mode hadoop mapred program, user can't download the
> logs programatically.
> jobclient.output.filter=ALL, allows user to print output in the stdout/stderr
> We need to have the ability to fetch the user logs from the framework.
> in 0.18, under the hod , we used to store the logs in the hdfs.
> For 0.20, as long as the jobhistory resides user can view the logs but then it's gone.
> So in short , I am proposing that hadoop
> 1) provide the options to the JobClient (i.e jobconf var jobclient.output.logs.location), so that it will download the output in the hdfs location instead of printing to stdout.
> Thanks
> Alok
> Alok
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.