riak crash

Hi all, I have my riak node crashed and can't figure out why this has happened. Any help would be appreciated. I'm using riak 1.3.1 and running a single node on CentOS 6.3 (availability is not critical right now). This node uses Bitcask backend with the default configuration except for expiry_sec

setting n_val

Hi all, I have a question regarding setting the n_val. In the documentation ( http://docs.basho.com/riak/latest/tutorials/fast-track/Tunable-CAP-Controls-in-Riak/) it is stated that: n_val must be greater than 0 and less than or equal to the number of actual nodes in your cluster to get all the b

Re: setting n_val

minimum is 5, but you could possibly get away with 3 (the > default repl value). > > There is a blog post about this from last year, explaining why: > http://basho.com/why-your-riak-cluster-should-have-at-least-five-nodes/ > > Eric > > On Jun 10, 2013, at 9:01 AM, Alexander Ily

Re: setting n_val

). > > The few times that I've built single-node apps (during hackathons, etc), I > usually go with option 2 (a), and backup/restore the data. But your use > case requirements may difer. > > Dmitri > > > > On Mon, Jun 10, 2013 at 12:01 PM, Alexander Ilyin > wrote: > &

memory consumption

Hi, I have a few questions about Riak memory usage. We're using Riak 1.3.1 on a 3 node cluster. According to bitcask capacity calculator ( http://docs.basho.com/riak/1.3.1/references/appendices/Bitcask-Capacity-Planning/) Riak should use about 30Gb of RAM for out data. Actually, it uses about 45Gb

Re: memory consumption

> On Fri, Aug 2, 2013 at 3:11 AM, Alexander Ilyin > wrote: > > Hi, > > > > I have a few questions about Riak memory usage. > > We're using Riak 1.3.1 on a 3 node cluster. According to bitcask capacity > > calculator > > ( > http://docs.basho.co

Re: memory consumption

t; 4 isn't amenable to anything other than a change in the way the keydir > is stored, which could also potentially help with 1 (fewer > allocations, etc). That, unfortunately, is not very likely to happen > soon. > > So things will get better relatively soon, but there are some

Re: memory consumption

one selects all keys larger than your fixed size, where you have > the fixed len - 8 as an additional overhead. > > On Tue, Aug 6, 2013 at 2:56 AM, Alexander Ilyin > wrote: > > So if you will succeed with all your patches the memory overhead will > > decrease by 22 (=16+4+2)

key expiration and memory

Hi, we're using Riak 1.3.1 with a Bitcask storage engine on a 4 node cluster. Properties of the bucket used: {"props":{"allow_mult":false," basic_quorum":false,"big_vclock":50,"chash_keyfun":{"mod":"riak_core_util","fun":"chash_std_keyfun"},"dw":"quorum","last_write_wins":false,"linkfun":{"mod":"r

Re: key expiration and memory

ossible to see how many keys were expired for the last >> minute/hour/day? > I don't think so - Bitcask doesn't send any notification to Riak when it > expires the keys, and I don't think it keeps any records of its own. > > > > On Wed, Aug 28, 2013 at 4:56 A

Re: key expiration and memory

y grows in this situation? In general, I want to know how to predict riak memory consumption (at least approximately). Because we aren't ready to buy new servers not knowing it. On 29 August 2013 14:44, Alexander Ilyin wrote: > Dmitri, > > yes, I have AAE turned on and this discuss

Re: key expiration and memory

Justin, app.config in the attachment. On 4 September 2013 20:13, Justin Shoffstall wrote: > Alexander, > >> * How I can ensure that merge process have enough time to delete old >> keys? May be it deletes them slower than new keys are added? > > Would you please attach the app.config files from o