Uses of Class
org.apache.hadoop.hbase.regionserver.MutableSegment
Packages that use org.apache.hadoop.hbase.regionserver.MutableSegment
-
Uses of org.apache.hadoop.hbase.regionserver.MutableSegment in org.apache.hadoop.hbase.regionserver
Methods in org.apache.hadoop.hbase.regionserver that return org.apache.hadoop.hbase.regionserver.MutableSegment in inModifier and TypeMethodDescriptionorg.apache.hadoop.hbase.regionserver.MutableSegmentSegmentFactory.createMutableSegment(org.apache.hadoop.conf.Configuration conf, CellComparator comparator, org.apache.hadoop.hbase.regionserver.MemStoreSizing memstoreSizing) Methods in org.apache.hadoop.hbase.regionserver with parameters of type org.apache.hadoop.hbase.regionserver.MutableSegment in inModifier and TypeMethodDescriptionprotected booleanCompactingMemStore.checkAndAddToActiveSize(org.apache.hadoop.hbase.regionserver.MutableSegment currActive, org.apache.hadoop.hbase.Cell cellToAdd, org.apache.hadoop.hbase.regionserver.MemStoreSizing memstoreSizing) Check whether anything need to be done based on the current active set size.org.apache.hadoop.hbase.regionserver.ImmutableSegmentSegmentFactory.createImmutableSegment(org.apache.hadoop.hbase.regionserver.MutableSegment segment, org.apache.hadoop.hbase.regionserver.MemStoreSizing memstoreSizing) protected voidAbstractMemStore.doAdd(org.apache.hadoop.hbase.regionserver.MutableSegment currentActive, org.apache.hadoop.hbase.ExtendedCell cell, org.apache.hadoop.hbase.regionserver.MemStoreSizing memstoreSizing) protected voidCompactingMemStore.flushInMemory(org.apache.hadoop.hbase.regionserver.MutableSegment currActive) protected abstract voidAbstractMemStore.postUpdate(org.apache.hadoop.hbase.regionserver.MutableSegment currentActive) Issue any post update synchronization and testsprotected voidCompactingMemStore.postUpdate(org.apache.hadoop.hbase.regionserver.MutableSegment currentActive) protected voidDefaultMemStore.postUpdate(org.apache.hadoop.hbase.regionserver.MutableSegment currentActive) protected abstract booleanAbstractMemStore.preUpdate(org.apache.hadoop.hbase.regionserver.MutableSegment currentActive, org.apache.hadoop.hbase.ExtendedCell cell, org.apache.hadoop.hbase.regionserver.MemStoreSizing memstoreSizing) Issue any synchronization and test needed before applying the updateprotected booleanCompactingMemStore.preUpdate(org.apache.hadoop.hbase.regionserver.MutableSegment currentActive, org.apache.hadoop.hbase.ExtendedCell cell, org.apache.hadoop.hbase.regionserver.MemStoreSizing memstoreSizing) Issue any synchronization and test needed before applying the update For compacting memstore this means checking the update can increase the size without overflowprotected booleanDefaultMemStore.preUpdate(org.apache.hadoop.hbase.regionserver.MutableSegment currentActive, org.apache.hadoop.hbase.ExtendedCell cell, org.apache.hadoop.hbase.regionserver.MemStoreSizing memstoreSizing) protected voidCompactingMemStore.pushActiveToPipeline(org.apache.hadoop.hbase.regionserver.MutableSegment currActive, boolean checkEmpty) NOTE: WhenCompactingMemStore.flushInMemory(MutableSegment)calls this method, due to concurrent writes and because we first add cell size to currActive.getDataSize and then actually add cell to currActive.cellSet, it is possible that currActive.getDataSize could not accommodate cellToAdd but currActive.cellSet is still empty if pending writes which not yet add cells to currActive.cellSet,so forCompactingMemStore.flushInMemory(MutableSegment),checkEmpty parameter is false.booleanCompactionPipeline.pushHead(org.apache.hadoop.hbase.regionserver.MutableSegment segment)