You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2011/09/01 02:47:11 UTC
[jira] [Created] (MAPREDUCE-2920) Local log dir links in the JT web
UI are broken
Local log dir links in the JT web UI are broken
-------------------------------------------------
Key: MAPREDUCE-2920
URL: https://issues.apache.org/jira/browse/MAPREDUCE-2920
Project: Hadoop Map/Reduce
Issue Type: Sub-task
Components: tasktracker
Affects Versions: 0.20.204.0
Reporter: Eli Collins
The task log servlet can no longer access user logs because MAPREDUCE-2415 introduce symlinks to the logs and jetty is not configured by default to follow symlinks (for security reasons).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MAPREDUCE-2920) Local log dir links in the JT
web UI are broken
Posted by "Eli Collins (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins resolved MAPREDUCE-2920.
------------------------------------
Resolution: Won't Fix
The task logs that are no longer available via logs/userlogs are available via the job history server (which works because it uses TaskLog to read the files instead of Jetty directly) so I don't think this is worth the effort of fixing.
> Local log dir links in the JT web UI are broken
> -------------------------------------------------
>
> Key: MAPREDUCE-2920
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2920
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: tasktracker
> Affects Versions: 0.20.204.0
> Reporter: Eli Collins
>
> The task log servlet can no longer access user logs because MAPREDUCE-2415 introduce symlinks to the logs and jetty is not configured by default to follow symlinks (for security reasons).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira