ASF GitHub Bot commented on NUTCH-2519:

sebastian-nagel closed pull request #287: NUTCH-2519 Log mapreduce job messages 
and counters in local mode
URL: https://github.com/apache/nutch/pull/287

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/conf/log4j.properties b/conf/log4j.properties
index e9e5e7f9f..6fad2b5d3 100644
--- a/conf/log4j.properties
+++ b/conf/log4j.properties
@@ -63,6 +63,8 @@ 
+# log mapreduce job messages and counters
 # Daily Rolling File Appender
@@ -71,7 +73,7 @@ log4j.logger.org.apache.hadoop=WARN
-# Rollver at midnight
+# Rollover at midnight
 # 30-day backup


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> 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
>            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

Reply via email to