Package | Description |
---|---|
org.apache.hadoop.hbase.regionserver |
Modifier and Type | Field and Description |
---|---|
private MutableSegment |
AbstractMemStore.active |
Modifier and Type | Method and Description |
---|---|
MutableSegment |
SegmentFactory.createMutableSegment(org.apache.hadoop.conf.Configuration conf,
CellComparator comparator,
MemStoreSizing memstoreSizing) |
private MutableSegment |
SegmentFactory.generateMutableSegment(org.apache.hadoop.conf.Configuration conf,
CellComparator comparator,
MemStoreLAB memStoreLAB,
MemStoreSizing memstoreSizing) |
(package private) MutableSegment |
AbstractMemStore.getActive() |
Modifier and Type | Method and Description |
---|---|
protected boolean |
CompactingMemStore.checkAndAddToActiveSize(MutableSegment currActive,
Cell cellToAdd,
MemStoreSizing memstoreSizing)
Check whether anything need to be done based on the current active set size.
|
ImmutableSegment |
SegmentFactory.createImmutableSegment(MutableSegment segment,
MemStoreSizing memstoreSizing) |
protected void |
AbstractMemStore.doAdd(MutableSegment currentActive,
Cell cell,
MemStoreSizing memstoreSizing) |
private void |
AbstractMemStore.doUpsert(MutableSegment currentActive,
Cell cell,
long readpoint,
MemStoreSizing memstoreSizing) |
protected void |
CompactingMemStore.flushInMemory(MutableSegment currActive) |
private void |
AbstractMemStore.internalAdd(MutableSegment currentActive,
Cell toAdd,
boolean mslabUsed,
MemStoreSizing memstoreSizing) |
private Cell |
AbstractMemStore.maybeCloneWithAllocator(MutableSegment currentActive,
Cell cell,
boolean forceCloneOfBigCell)
If the segment has a memory allocator the cell is being cloned to this space, and returned;
Otherwise the given cell is returned When a cell's size is too big (bigger than maxAlloc), it
is not allocated on MSLAB.
|
protected void |
CompactingMemStore.postUpdate(MutableSegment currentActive) |
protected void |
DefaultMemStore.postUpdate(MutableSegment currentActive) |
protected abstract void |
AbstractMemStore.postUpdate(MutableSegment currentActive)
Issue any post update synchronization and tests
|
protected boolean |
CompactingMemStore.preUpdate(MutableSegment currentActive,
Cell cell,
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 overflow
|
protected boolean |
DefaultMemStore.preUpdate(MutableSegment currentActive,
Cell cell,
MemStoreSizing memstoreSizing) |
protected abstract boolean |
AbstractMemStore.preUpdate(MutableSegment currentActive,
Cell cell,
MemStoreSizing memstoreSizing)
Issue any synchronization and test needed before applying the update
|
protected void |
CompactingMemStore.pushActiveToPipeline(MutableSegment currActive,
boolean checkEmpty)
NOTE: When
CompactingMemStore.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 for
CompactingMemStore.flushInMemory(MutableSegment) ,checkEmpty parameter is false. |
boolean |
CompactionPipeline.pushHead(MutableSegment segment) |
private void |
CompactingMemStore.tryFlushInMemoryAndCompactingAsync(MutableSegment currActive)
Try to flush the currActive in memory and submit the background
CompactingMemStore.InMemoryCompactionRunnable to
RegionServicesForStores.getInMemoryCompactionPool() . |
Copyright © 2007–2020 The Apache Software Foundation. All rights reserved.