Re: ANN: Riak C Client *alpha*

Thanks, Rob. I'm taking a look right now at hiredis. Love the async abstraction. Cleans a few things up. I'll look at tweaking our design accordingly. With solidarity in C, Brett On 10/31/13 11:54 AM, Robert Zuber wrote: hiredis has a model for pluggable event loops in a C client lib that

[ANN] RICON West 2013 Survey & Videos

Hi All, With another RICON put to rest we're already busy scheming up how we can improve the content and experience next year. In that vein, if you attended RICON West in person or watched the talks over the live stream we'd greatly appreciate your feedback. We've created a survey [0] which shoul

Re: RFC: Let's Make Riak-Core Easier to Use

Hi. We have two system based on riak-core. Simple distributed database for storing time-series data, we don't use riak_kv for this because we need batch insert,our data are small(16 byte key and 12 byte value) and we need less consistence guarantee but lowest latency. The second is framework named

Re: tuning number of async threads in Riak's default pool

+A changes the size of the erlang asynchronous IO thread pool. Since eleveldb doesn't use that thread pool, you can tune it down, but since it doesn't take up a lot of resources, there is generally no reason to do so. On Fri, Nov 1, 2013 at 11:48 AM, kzhang wrote: > Thanks! > > Could you elabora

Re: tuning number of async threads in Riak's default pool

Thanks! Could you elaborate on it? -- View this message in context: http://riak-users.197444.n3.nabble.com/tuning-number-of-async-threads-in-Riak-s-default-pool-tp4029628p4029666.html Sent from the Riak Users mailing list archive at Nabble.com. ___

Re: tuning number of async threads in Riak's default pool

You should probably leave it at its default value. On modern systems there is no reason to change that value. On Fri, Nov 1, 2013 at 11:02 AM, kzhang wrote: > Does anyone have any insight? > > > > -- > View this message in context: > http://riak-users.197444.n3.nabble.com/tuning-number-of-async

Re: tuning number of async threads in Riak's default pool

Does anyone have any insight? -- View this message in context: http://riak-users.197444.n3.nabble.com/tuning-number-of-async-threads-in-Riak-s-default-pool-tp4029628p4029664.html Sent from the Riak Users mailing list archive at Nabble.com. ___ riak-u

Re: bitcask issue - write_locked

Thanks for the heads-up sounds simple enough to add to the Riak startup script in /etc/init.d On Fri, Nov 1, 2013 at 10:30 AM, Evan Vigil-McClanahan wrote: > I replied to this (accidentally) off-list. For the rest of you folks, > if you want to follow the resolution you can add yourself to the >

Re: bitcask issue - write_locked

I replied to this (accidentally) off-list. For the rest of you folks, if you want to follow the resolution you can add yourself to the following issue: https://github.com/basho/bitcask/issues/99 In the mean time, a workaround is to remove all lockfiles (bitcask.*.lock) from your bitcask director

Re: RFC: Let's Make Riak-Core Easier to Use

+1 for better docs, progressive examples, and better tooling On Tue, Oct 29, 2013 at 7:13 PM, Sam Elliott wrote: > Hey Riak-Users (and Riak-Core) > > Some time ago, Basho released riak_core as a framework for building > distributed applications [1]. > One of the key pieces of guidance that was