ss than or equal to the number of
>> actual nodes in your cluster to get all the benefits of replication.
>> And, we advise against modifying the n_val of a bucket after its initial
>> creation as this may result in failed reads because the new
>> value may not be replicated to all
gt;
> But this seems contradictory to me. Which value I have to set if I'm
> setting up one node right now but planning to add second one later?
> Setting n_val=2 means this value will be greater than actual number of
> nodes. But setting n_val=1 is also not advisable since
> I w
this seems contradictory to me. Which value I have to set if I'm
> setting up one node right now but planning to add second one later?
> Setting n_val=2 means this value will be greater than actual number of
> nodes. But setting n_val=1 is also not advisable since
> I will
> value may not be replicated to all the appropriate partitions.
>
> But this seems contradictory to me. Which value I have to set if I'm setting
> up one node right now but planning to add second one later?
> Setting n_val=2 means this value will be greater than actual number o
o me. Which value I have to set if I'm setting
> up one node right now but planning to add second one later?
> Setting n_val=2 means this value will be greater than actual number of nodes.
> But setting n_val=1 is also not advisable since
> I will have to change it later to n_v
tting up one node right now but planning to add second one later?
Setting n_val=2 means this value will be greater than actual number of
nodes. But setting n_val=1 is also not advisable since
I will have to change it later to n_val=2 (I'm planning to have two
replicas in the end).
I'm also
Hi,
I was writing some unit tests and got a surprise when the http api did not
respond with the expected 400 status code when I set the n_val bucket property
to a negative number. When I fetched the bucket property, Riak cheerfully told
me the value was indeed negative.
Are negative numbers va
