Timo, Here are some rough concepts of leveldb:
- Compaction in leveldb is triggered by input activity, not by key age or key delete. - A key delete does not actually delete a key, it creates a "tombstone". - Old values of a key only get purged if two versions of the key happen to participate in the same compaction. Then the oldest is dropped. Therefore, it is not easy to estimate the length of time before all your 1 to 3Mb objects purge. They will purge and free up disk space eventually … but not necessarily quickly. There is currently no means for a user to initiate targeted compactions to address your situation. You will just have to wait. Matthew On Sep 13, 2013, at 2:14 AM, Timo Gatsonides <t...@me.com> wrote: > > I'm running a database where the values are typically fairly large (1-3Mb). > Now I'm planning to remove older data (>1 year ago) by moving it into Glacier > and only keeping some metadata in the database. I am currently planning to > remove the content of any K/V itself (object.raw_data in the Ruby client) and > setting some Meta tags as to where the data is stored in Glacier and the > encryption keys for retrieval and decryption if the data is ever needed. > > Now my question is: will this trigger a compaction in LevelDB? If so, when > will it trigger? Is there some way to monitor this, is there for example a > specific log entry when compaction is triggered? > > Or will it maybe only trigger if the key is completely removed, then I'll > simply save the metadata to another key, e.g. append "-removed" to the key or > in another bucket? > > Thanks for any feedback, > Timo > > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
