Re: question about namenode log spam

2010-10-23 Thread Stack
like this to >> hadoop/conf/log4j.properties on your namenode: >> >> log4j.logger.org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit=WARN >> >> Best regards, >> >>    - Andy >> >> >> --- On Fri, 10/22/10, Jack Levin wrote: >> >>> From: Jack Levin >>> Subject: questio

Re: question about namenode log spam

2010-10-23 Thread Andrew Purtell
> Any tips on how to find out which dfs 'client' is > talking to namenode? I've never needed to do this, sorry. Maybe others know. Odd and unhelpful that the audit messages don't carry this information. - Andy

Re: question about namenode log spam

2010-10-22 Thread Jack Levin
g you can add a line like this to > hadoop/conf/log4j.properties on your namenode: > > log4j.logger.org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit=WARN > > Best regards, > >    - Andy > > > --- On Fri, 10/22/10, Jack Levin wrote: > >> Fr

Re: question about namenode log spam

2010-10-22 Thread Andrew Purtell
estion about namenode log spam > To: user@hbase.apache.org > Date: Friday, October 22, 2010, 1:07 PM > Ok, I am not running any fsck right > now, but my namenode log file gets > flooded with: > > > 2010-10-22 13:05:35,695 INFO > org.apache.hadoop.hdfs.server.namenode.FSN

question about namenode log spam

2010-10-22 Thread Jack Levin
Ok, I am not running any fsck right now, but my namenode log file gets flooded with: 2010-10-22 13:05:35,695 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: ugi=nullip=null cmd=open src=/hbase/img_attrib2/1013787254/at/6389043051467581294dst=null pe