Hi - I have a Riak node with n_val=3, r=2, w=2 and have just one key-object
stored there-in. I'm trying to test various configurations to better
understand the system and have the following observations - some dont seem
to align with my understanding so far, so appreciate if someone can throw
some
Vikram,
John Daily wrote a fantastic blog series that places your question in
context and then answers it.
http://basho.com/posts/technical/understanding-riaks-configurable-behaviors-part-1/
Tom
On Wed, Jul 27, 2016 at 4:07 PM, Vikram Lalit wrote:
> Hi - I have a Riak node with n_val=3, r=2,
Thanks Tom... Yes I did read that but I couldn't deduce the outcome if n is
decreased. John talks about data loss, but am actually observing a
different result... perhaps am missing something!
On Wed, Jul 27, 2016 at 6:11 PM, Tom Santero wrote:
> Vikram,
>
> John Daily wrote a fantastic blog se
Hello!
We are experiencing error messages from the client that we don’t totally
understand. They look like the following:
Checking the riak error and crash logs, I’m seeing “overload” errors which I
assume is causing the “no response from backend” client errors:
{error,
badarg,
[{erlang,io
Vikram,
I apologize, I initially just skimmed your question and thought you were
asking something entirely different.
While increasing your N value is safe, decreasing it on a bucket with
pre-existing data, as you have, is not-recommended and the source of your
inconsistent results.
Tom
On Wed,
Hi Chris,
This sounds like the issue described at
https://github.com/basho/riak_kv/issues/1418
On Wed, Jul 27, 2016 at 11:19 PM, wrote:
> Also, does anyone have any recommendations on query pooling so we can
> guarantee that multiple clients will not generate more queries than the
> cluster c
Hi Cian,
Thank you! I should've mentioned in my initial email that I thought we were
experiencing the same bug you called out (in fact the 2nd comment on that
github issue is actually from me).
So, what I'm really curious about is whether or not the original "overload"
error is happening becau