MemoryManager (Apache Accumulo Server Base 1.10.4 API)

All Known Implementing Classes:

LargestFirstMemoryManager
```
public interface MemoryManager
```
A MemoryManager in accumulo currently determines when minor compactions should occur and when ingest should be put on hold. The goal of a memory manager implementation is to maximize ingest throughput and minimize the number of minor compactions.

Method Summary

All Methods Instance Methods Abstract Methods
Modifier and Type	Method	Description
`MemoryManagementActions`	`getMemoryManagementActions(List<TabletState> tablets)`	An implementation of this function will be called periodically by accumulo and should return a list of tablets to minor compact.
`void`	`init(ServerConfiguration conf)`	Initialize the memory manager.
`void`	`tabletClosed(KeyExtent extent)`	This method is called when a tablet is closed.

- Method Detail
  - init
```
void init(ServerConfiguration conf)
```
    Initialize the memory manager.
  - getMemoryManagementActions
```
MemoryManagementActions getMemoryManagementActions(List<TabletState> tablets)
```
    An implementation of this function will be called periodically by accumulo and should return a list of tablets to minor compact. Instructing a tablet that is already minor compacting (this can be inferred from the TabletState) to minor compact has no effect. Holding all ingest does not affect metadata tablets.
  - tabletClosed
```
void tabletClosed(KeyExtent extent)
```
    This method is called when a tablet is closed. A memory manger can clean up any per tablet state it is keeping when this is called.