[
https://issues.apache.org/jira/browse/NUTCH-2519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387472#comment-16387472
]
Hudson commented on NUTCH-2519:
-------------------------------
SUCCESS: Integrated in Jenkins build Nutch-trunk #3504 (See
[https://builds.apache.org/job/Nutch-trunk/3504/])
NUTCH-2519 Log mapreduce job messages and counters in local mode (snagel:
[https://github.com/apache/nutch/commit/ae30dff285b8619467e9c838787acd3a4aba42fb])
* (edit) conf/log4j.properties
> Log mapreduce job counters in local mode
> ----------------------------------------
>
> Key: NUTCH-2519
> URL: https://issues.apache.org/jira/browse/NUTCH-2519
> Project: Nutch
> Issue Type: Improvement
> Affects Versions: 2.3.1, 1.14
> Reporter: Sebastian Nagel
> Assignee: Sebastian Nagel
> Priority: Trivial
> Fix For: 2.4, 1.15
>
>
> A simple change in the log4j.properties would make the Hadoop job counters
> appear in the hadoop.log also in local mode:
> {noformat}
> log4j.logger.org.apache.hadoop.mapreduce.Job=INFO
> {noformat}
> This may provide useful information for debugging, esp. if counters are not
> explicitly logged by tools (see
> [@user|https://lists.apache.org/thread.html/1dd5410b479bd536fb3df98612db4b832cd0a97533099b0dc632eba9@%3Cuser.nutch.apache.org%3E]).
> This would make the output also more similar to (pseudo)distributed mode
> (Nutch is called via {{hadoop jar}}) Job counters and progress info are
> obligatorily logged.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
