1
0
Fork 0

minor adjustments

This commit is contained in:
jsteemann 2017-02-21 15:49:47 +01:00
parent ebbfeaead9
commit d27360fd04
1 changed files with 9 additions and 9 deletions

View File

@ -1,19 +1,19 @@
MMFilesEngine
=============
How operations are Stored - Overview
How operations are stored - Overview
------------------------------------
All operations like insert or delete are written as markers to a write ahead
log (WAL). This WAL consists of slices of a certain size and if such a slice is
full for is manually flushed all relevant markers are transferred
All operations like insert or remove are written as markers to a write ahead
log (WAL). This WAL consists of files of a certain size and if such a file is
full (or is manually flushed), all relevant markers are transferred
(transferMarkers()) to the journals of the respective collections. During the
transfer obsolete markers will be thrown away: a sequence of insert, remove,
transfer any obsolete markers will be thrown away: a sequence of insert, remove,
insert on the same document will result in the last insert discarding the
previous operations. When a journal file of size (journalSize()) is full it
will be sealed and renamed. By applying this operations it will become a
datafile, that is read only. Datafiles will eventually be merged by a compactor
task/thread, that does the about the same work as the transferMarkers function
previous operations. When a journal file of size (journalSize()) is full, it
will be sealed and renamed. By applying these operations it will become a
datafile that is read-only. Datafiles will eventually be merged by a compactor
thread that does the about the same work as the transferMarkers function,
reducing the size of the stored data.
Ditches