[
https://issues.apache.org/jira/browse/MAPREDUCE-5148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13651696#comment-13651696
]
Arun C Murthy commented on MAPREDUCE-5148:
------------------------------------------
[~yeshavora] finally helped me understand the issue. The problem is that if
there is an existing install, and people just upgrade the hadoop-core jar it
breaks them and is, as such, a problem.
Maybe a simple fix is to include task-log4j.properties in the hadoop-core jar?
Something like:
{noformat}
diff --git build.xml build.xml
index a87513c..d5a3859 100644
--- build.xml
+++ build.xml
@@ -762,7 +762,7 @@
<tarfileset dir="bin" mode="755"/>
</tar>
<property name="jar.properties.list"
- value="commons-logging.properties, log4j.properties,
hadoop-metrics.properties"/>
+ value="commons-logging.properties, log4j.properties,
hadoop-metrics.properties, task-log4j.properties"/>
<jar jarfile="${build.dir}/${core.final.name}.jar"
basedir="${build.classes}">
<manifest>
{noformat}
> Syslog missing from Map/Reduce tasks
> ------------------------------------
>
> Key: MAPREDUCE-5148
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5148
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 1.2.0
> Reporter: yeshavora
> Attachments: Screenshot_MAPREDUCE-5148.png
>
>
> MAPREDUCE-4970 introduced incompatible change and causes syslog to be missing
> from tasktracker on old clusters which just have log4j.properties configured
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
