Ah, that makes sense. Would it make sense to default the root logger to
the one defined in log4j.properties file instead of the static value in
the script then? That way an admin can set all logging properties
desired in the log4j.properties file, but can override with
HADOOP_ROOT_LOGGER to d
It's not always practical to edit the log4j.properties file. For one
thing, if you're using a management system, there may be many log4j
properties sprinkled around the system, and it could be difficult to figure
out which is the one you need to edit. For another, you may not (should
not?) have p
In my experience the default HADOOP_ROOT_LOGGER definition will override
any root logger defined in log4j.properties, which is where the problems
have arisen. If the HADOOP_ROOT_LOGGER definition in hadoop-config.sh
were removed, wouldn't the root logger defined in the log4j.properties
file be
Hi Robert,
I understand your confusion.
HADOOP_ROOT_LOGGER is set to default value "INFO,console" if it hasn't set
for anything and logs will be displayed on the console itself.
This will be true for any client commands you run. For ex: "hdfs dfs -ls /"
But for the server scripts (hadoop-daemon.
