A vacuum command would be most appropriate...
On Fri, Jul 26, 2013 at 11:16 AM, Jordan West wrote:
> To clarify a bit further:
>
> If you started with a fresh 1.4 cluster (or explicitly changed the
> app.config setting) you are using a new on-disk format that applies to any
> backend used by Ri
To clarify a bit further:
If you started with a fresh 1.4 cluster (or explicitly changed the
app.config setting) you are using a new on-disk format that applies to any
backend used by Riak, including LevelDB. There new format is more compact
but, like MvM said, the majority of savings here probabl
/ Stockholm / Vienna
Subject: Re: Riak 1.4.0: *Massive* disk space saving with eLevelDB
Dave,
Glad you are happy.
The truth is that you gained space via the backup/restore process. The data
formats of 1.3.1 and 1.4 are the same.
leveldb only removes dead / old key/values during its backg
Dave,
Glad you are happy.
The truth is that you gained space via the backup/restore process. The data
formats of 1.3.1 and 1.4 are the same.
leveldb only removes dead / old key/values during its background compaction.
It could be days, even weeks in some cases, between when you write fresh
Thank you Basho for the new on-disk format changes to eLevelDB!
We have just migrating from 1.3.1 to 1.4.0, and since we wanted to change the
ring size too, we used Dan Kerrigan's Data Migrator to backup/restore our
buckets.
The space savings are very impressive! Each node went from using a
