105 Commits

Author	SHA1	Message	Date
Calle Wilund	aeb83f2874	Add commitlog to db + use it in storage_proxy/handler ... * A commitlog is created in "work" dirs when initing the db from a datadir. However, since we have neither disk data storage, nor replay capability yet (and no real db config), the settings are basically to just write in-memory serialization, write them to disk and then discard them. So in fact, pointless. But at least using the log... * Moved the actual "apply" of mutation into database. If a commitlog is active, add an entry to it before applying mutation.	2015-04-29 10:10:21 +02:00
Calle Wilund	07f1208926	Make commitlog respect max disk size setting.	2015-04-29 10:10:21 +02:00
Calle Wilund	9979ee8d45	Modify commit log to use dataoutput ... Both internal usage and external interface.	2015-04-01 10:08:00 +02:00
Calle Wilund	80b244cc4b	commitlog: fix using wrong segment ... Commit log segment "finish_and_get_new" should not call "new_segment" explicitly, since more than one invocation might get there on the same flush condition (segment full). Signed-off-by: Calle Wilund <calle@cloudius-systems.com>	2015-03-09 17:54:47 +02:00
Calle Wilund	054f9ed082	Initial commit log support. ... Implements a cassandra-file-compatible segmented log of "mutations". Handles "batch" and "periodic" mode like stock version. Also includes "dirty" management for the interaction log/memtable. Supports: * add * sync/flush * clear dirty bits (thus discarding segments) Many more estoric stock functions not yet implemented. Missing: Storage management. Does not deal with total size on disk of segments yet. Nor does it have any provisions for dealing with active buffer bloat should async writes stall. [avi: adjust for future<>::rescue() removal] Signed-off-by: Calle Wilund <calle@cloudius-systems.com>	2015-03-05 11:06:09 +02:00