Influxdata
/
influxdb
mirror of https://github.com/influxdata/influxdb.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

doc: refine description of the conclusion of the compaction process. 

Signed-off-by: Jon Seymour <jon@wildducktheories.com>
pull/5678/head
Jon Seymour 2016-02-13 17:24:37 +11:00
parent 008af05f7b
commit 285e0ad17a
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tsdb/engine/tsm1/DESIGN.md
View File

@ -97,7 +97,7 @@ The compaction is used to generate a set of SeriesIterators that return a sequen
Deletions can occur while a new file is being written. Since the new TSM file is not complete a tombstone would not be written for it. This could result in deleted values getting written into a new file. To prevent this, if a compaction is running and a delete occurs, the current compaction is aborted and new compaction is started.
When all files are processed and successfully written, completion checkpoint markers are created and files are renamed. The engine then notifies the Cache of the checkpoint of the compaction which is used for by the Cache to know what entries can be evicted in the future.
When all WAL files in the current compaction have been processed and the new TSM files have been successfully written, completion checkpoint markers are created and the new TSM files are renamed to their final names. The engine then notifies the Cache of the checkpoint of the compaction which is used by the Cache to learn which entries may be evicted in the future.
The compaction process then runs again until there are no more WAL files and the minimum number of TSM files exist that are also under the maximum file size.