hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-16155) Compacting Memstore : Few log improvements
Date Thu, 30 Jun 2016 14:09:10 GMT
Anoop Sam John created HBASE-16155:
--------------------------------------

             Summary: Compacting Memstore : Few log improvements
                 Key: HBASE-16155
                 URL: https://issues.apache.org/jira/browse/HBASE-16155
             Project: HBase
          Issue Type: Sub-task
            Reporter: Anoop Sam John
            Assignee: Anoop Sam John


When testing this I can see large log files for RS. Many log lines in INFO level which can
be lower level

LOG.info("FLUSHING TO DISK: region "+ getRegionServices().getRegionInfo()
          .getRegionNameAsString() + "store: "+ getFamilyName());
To be DEBUG
LOG.info("IN-MEMORY FLUSH: Pushing active segment into compaction pipeline, " +
          "and initiating compaction.");
To be DEBUG
LOG.info("Swapping pipeline suffix with compacted item. "
          +"Just before the swap the number of segments in pipeline is:"
          +versionedList.getStoreSegments().size()
          +", and the number of cells in new segment is:"+segment.getCellsCount()); 
To be DEBUG		  
LOG.info("Suffix size: "+ suffixSize+" compacted item size: "+newSize+
          " globalMemstoreSize: "+globalMemstoreSize);
To be DEBUG		  
LOG.info("Starting the MemStore in-memory compaction for store " +
        compactingMemStore.getStore().getColumnFamilyName());
To be DEBUG		

And one now in DEBUG can be better at INFO level
LOG.debug("Setting in-memory flush size threshold to " + inmemoryFlushSize);




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message