Reid is correct. Also be aware that the new default will be 128, which is
what the HTTP interface has used for a long time and has caused no issues,
as far as I know.
On Wed, Jan 15, 2014 at 5:38 PM, Reid Draper wrote:
> I know many users who have had success with numbers in the 128-256 range.
I know many users who have had success with numbers in the 128-256 range. There
should be no harm in cranking it up pretty high. The ‘formula’ would just be
the number of concurrent connection handshakes you want to be able to handle.
Reid
On Jan 15, 2014, at 5:26 PM, Alain Rodriguez wrote:
>
Hi all,
Can anyone share some wisdom on what to set pb_backlog to? Is there some
kind of formula based on the number of requests/s?
I am seeing a ton of connection timeouts when I restart my application and
I have pb_backlog set to the default of 5.
Thanks,
Alain
___
Morning, Afternoon, Evening to All -
We've got a great Recap for today. Enjoy and thanks for being a part of Riak.
Mark
twitter.com/pharkmillups
---
Riak Recap for January 8 - 14
==
Basho rolled out some new product options for commercial supp
There was a patch for Bitcask to do this by jtuple a couple years back. Not
sure it made it into a release.
See:
http://lists.basho.com/pipermail/riak-users_lists.basho.com/2011-March/003608.html
—John
> Date: Tue, 14 Jan 2014 10:38:23 -0800
> From: Matthew MacClary
> To: riak-users@lists.ba
Eric,
Seems yokozuna is what I looked for.
The only problem is our project is already in production.
Are there any other ways like additional buckets serving as indexes or
something built-in to achieve similar functionality?
Is there a way in Riak to get values for several known keys without using