FAQ
How can I prevent the following messages from creating huge datanode logs ?

2010-09-22 00:00:00,030 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /10.110.210.11:50010, dest: /10.110.210.11:34714, bytes: 132096, op: HDFS_READ, cliID: DFSClient_-5111
26949, srvID: DS-1397488018-10.110.210.11-50010-1281421533434, blockid: blk_-7124017481313431390_57263
2010-09-22 00:00:00,031 INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /10.110.210.11:50010, dest: /10.110.210.11:34715, bytes: 132096, op: HDFS_READ, cliID: DFSClient_-5111
26949, srvID: DS-1397488018-10.110.210.11-50010-1281421533434, blockid: blk_-7124017481313431390_57263


I guess there should be a log4j property, can't figure out which one. I already have root.logger set to WARN. Shouldn't this set all messages to WARN?
Also, will I need to restart hdfs to get changes into effect?
Thanks,
Avani Sharma
Trust and Safety, Applied Research
eBay, Inc. San Jose, CA
408-376-5398

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-user @
categorieshadoop
postedSep 22, '10 at 11:38p
activeSep 22, '10 at 11:38p
posts1
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Sharma, Avani: 1 post

People

Translate

site design / logo © 2022 Grokbase