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=null ip=null cmd=open src=/hbase/img_attrib2/1013787254/at/6389043051467581294 dst=null perm=null 2010-10-22 13:05:35,695 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: ugi=null ip=null cmd=open src=/hbase/img_attrib2/1013787254/at/7974496752278492374 dst=null perm=null 2010-10-22 13:05:35,695 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: ugi=null ip=null cmd=open src=/hbase/img_attrib2/1015465179/.regioninfo dst=null perm=null 2010-10-22 13:05:35,695 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: ugi=null ip=null cmd=open src=/hbase/img_attrib2/1015465179/at/3898058552498687797 dst=null perm=null 2010-10-22 13:05:35,695 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: ugi=null ip=null cmd=open src=/hbase/img_attrib2/1015465179/at/6614723640876741495 dst=null perm=null 2010-10-22 13:05:35,695 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: ugi=null ip=null cmd=open src=/hbase/img_attrib2/1020292229/.regioninfo dst=null perm=null 2010-10-22 13:05:35,695 INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem.audit: ugi=null ip=null cmd=open src=/hbase/img_attrib2/1020292229/at/1982596761753054075 is it possible to track down to which client is requesting it? Namenode literally opens every file every 20 seconds or so. Is something master doing to the HDFS? Can I turn off "INFO" logging somehow? -Jack
