Its NN logging block status changes. In distributed mode, its in the NN log. The logger has a particular key so it'd be easy enough to turn off just this logging. The key is BlockStateChange from NameNode.java. In fact in hdfs log4j.properties, I see this commented out, #log4j.logger.BlockStateChange=WARN, so likely disabling a pretty common practise. St.Ack
On Tue, Jul 15, 2014 at 11:01 AM, Vladimir Rodionov <[email protected]> wrote: > 2.2. What comes by default with HBase 0.98.3 hadoop2 > > I run tests in a local mode with HBase mini cluster. > > best, > -Vladimir Rodionov > > > On Tue, Jul 15, 2014 at 10:59 AM, Stack <[email protected]> wrote: > > > Which hdfs version V? > > St.Ack > > > > > > On Tue, Jul 15, 2014 at 10:57 AM, Vladimir Rodionov < > > [email protected]> > > wrote: > > > > > I do some performance testing of parallel scanners over the same store > > file > > > > > > I insert data, than major compact it , make sure that I have only one > > > region with only one store file. Than I run tests. Sometimes, during > > tests > > > I see the following messages in a log file (lot of them): > > > > > > 2014-07-15 10:54:00,378 [INFO|BlockStateChange|BlockManager] BLOCK* > > > addToInvalidates: blk_1073742034_1210 127.0.0.1:49599 > > > > > > Can someone tell me what do they mean? > > > > > > best, > > > > > > -Vladimir Rodionov > > > > > > PS > > > > > > HBase 0.98.3 > > > > > >
