Changing the r,w values on the client side fixed my problem... Thanks!
--Matthew
On Wed, Apr 28, 2010 at 13:44, Sean Cribbs wrote:
> Not currently. The defaults are hard-coded in the HTTP resource as:
> r = 2, w = 2, dw = 0, rw = 2
>
> Sean Cribbs
> Developer Advocate
> Basho Technologies,
Not currently. The defaults are hard-coded in the HTTP resource as:
r = 2, w = 2, dw = 0, rw = 2
Sean Cribbs
Developer Advocate
Basho Technologies, Inc.
http://basho.com/
On Apr 28, 2010, at 1:38 PM, Matthew Pflueger wrote:
> Stupid question: Is there a way to set the default read values for
On Wed, Apr 28, 2010 at 1:38 PM, Matthew Pflueger
wrote:
> Stupid question: Is there a way to set the default read values for a
> request on the server side when a client doesn't explicitly set them?
Not currently. The defaults at this time are in the client libraries.
-Justin
___
Stupid question: Is there a way to set the default read values for a
request on the server side when a client doesn't explicitly set them?
--Matthew
On Wed, Apr 28, 2010 at 12:38, Justin Sheehy wrote:
> If the N value for the bucket is lower than the R or W value in a
> request, then the reque
If the N value for the bucket is lower than the R or W value in a
request, then the request cannot succeed. That sounds likely in this
case. An upcoming release will provide more useful messages when
someone makes that particular client error.
-Justin
On Wed, Apr 28, 2010 at 12:35 PM, Matthew
Doing what Sean suggested worked (or just specifying the chash_fun in
the default_bucket_props). Now I'm running into weird behavior that
I'm guessing is related to the n_val setting. I'm running three nodes
all on separate machines joined with a ring partition size of 64
(22,21,21). On a fourth
We used to have a function that would merge the values from app.config with the
hardcoded defaults for bucket properties. I've opened an issue on bugzilla for
this problem (Bug 123). In the meantime, remove the stuff you've set, start up
the console, and run this in the Erlang shell:
applicati
Forgot to say I'm using riak-0.10.1...
--Matthew
On Wed, Apr 28, 2010 at 10:56, Matthew Pflueger
wrote:
> I am trying to set the default n_val in my app.config. I'm not
> getting any errors on startup but when a client tries to put some data
> a process crashes eventually causing a time-out o
I am trying to set the default n_val in my app.config. I'm not
getting any errors on startup but when a client tries to put some data
a process crashes eventually causing a time-out on the client side...
app.config part:
[
%% Riak Core config
{riak_core, [
%% Default location of