Re: how to really delete keys from Riak

2016-04-20 Thread Daniel Abrahamsson
If you have much more short lived data than long lived data, tuning the bitcask merge settings might help. Note that more frequent merging also means more CPU and I/O usage. I recently switched over to multi-backend exactly to deal with data in different buckets having different life spans. The ma

Re: how to really delete keys from Riak

2016-04-20 Thread Daniel Abrahamsson
As Alexander points out, the bitcask auto expiry feature [1] seems to fit your use case. You should also have a look at your bitcask merge settings [1] and your logs, to ensure merges are triggered when you want them to. [1] http://docs.basho.com/riak/kv/2.0.6/configuring/backend/#bitcask //Danie

Re: how to really delete keys from Riak

2016-04-20 Thread Shifeng Xiao
Thanks for the information Alexander and Daniel, I appreciated it. We are using Riak2.0 and bitcask as backend, and we are writing the keys once into bucket, keep it for a few hours, then delete it, never update the existing data. On Wed, Apr 20, 2016 at 11:32 AM, Alexander Sicular wrote: > Hel

Riak TS -- Multi Value Columns

2016-04-20 Thread Harjot Gill
Hi, We are evaluating using Riak TS (vs. Druid) as our time series data. We require ability to query rows by tags. I have a couple of questions: 1. Is there support for Multi-value columns? I believe it is possible with Secondary Indexes in Riak KV. Any idea when this might be supported in Ri

Re: how to really delete keys from Riak

2016-04-20 Thread Alexander Sicular
Check out bitcask TTL, expiry. -Alexander @siculars http://siculars.posthaven.com Sent from my iRotaryPhone > On Apr 20, 2016, at 12:20, Shifeng Xiao wrote: > > Thanks for the information Alexander and Daniel, I appreciated it. > > We are using Riak2.0 and bitcask as backend, and we are wr

Re: how to really delete keys from Riak

2016-04-20 Thread Alexander Sicular
Hello Shifeng, Riak uses Bitcask as its default data backend, it may also use leveldb as a backend but must be configured to do so[0][1]. Both bitcask[2] and leveldb[3] do not reclaim disk space immediately when a delete is issued. Incidentally, neither do updates. Because Riak is non-destructive,

Riak TS -- Multi Value Columns

2016-04-20 Thread Harjot Gill
Hi, We are evaluating using Riak TS (vs. Druid) as our time series data. We require ability to query rows by tags. I have a couple of questions: 1. Is there support for Multi-value columns? I believe it is possible with Secondary Indexes in Riak KV. Any idea when this might be supported in Ri

Re: how to really delete keys from Riak

2016-04-20 Thread Daniel Abrahamsson
Hi, What riak version and what riak backend are you using? For leveldb you have to take compaction into account, and for older bitcask versions there are known issues with data not being properly deleted. //Daniel ___ riak-users mailing list riak-users@

how to really delete keys from Riak

2016-04-20 Thread Shifeng Xiao
Hi, We are using Riak in production, but hit an issue that 80% of keys are deleted in Riak through Erlang API http://basho.github.io/riak-erlang-client/riakc_pb_socket.html#delete-3, but we only got 5% disk space saving, we expect 80% disk space saving, can anyone please help me? Thanks. Shife

Riak TS -- Multi Value Columns

2016-04-20 Thread Harjot Gill
Hi, We are evaluating using Riak TS (vs. Druid) as our time series data. We require ability to query rows by tags. I have a couple of questions: 1. Is there support for Multi-value columns? I believe it is possible with Secondary Indexes in Riak KV. Any idea when this might be supported in Ri