Thanks again for the insight, I did lower the frequency and expiration
dates a bit. I'm sure that will resolve itself when actual data is in use.
I have made further development with the proxying issue, as far as
narrowing it down to client_body_buffer_size:
http://nginx.org/en/docs/http/ngx_http_
Andrew,
There is no tuning necessary for read-repairs. They happen automatically, but
only when you read the object. So if your access pattern involves frequent read
access to your data the repairs will just happen.
The other option is active anti-entropy. This is basically a way for Riak to
Thanks again, Kelly, for your response.
I continued playing with things last night and
updated fold_objects_for_list_keys across the nodes to be true and
performed a full roll of the stack, that seems to have sped up the replies.
But, the lol bucket was still returning differing results.
I added
Andrew,
Are you able to successfully download all the files in the lol bucket? It seems
like you have some replicas in Riak that do not have copies of all of the data
from that bucket. That can be resolved in two ways: read-repair or active
anti-entropy. So I would expect doing a read of each o
I appreciate the help Kelly! ( And sorry for the double mail you're going
to get, accidentally didn't reply to all. ) I've provided the requested
information below.
app.config:
http://pastebin.centos.org/5716/
app.config for riak-cs is managed by puppet, installing the same file on
both nodes.
r
Andy,
To try to get a better idea of what might be going on it would be helpful to
see what your riak and riak cs app.config files look like. Also the output of
riak-admin ring-status and riak-admin member-status could be useful. For the
upload issue I am curious if you have changed the port th
Hey guys,
I'm working on a dev environment for a riak-cs setup.
2 vms and an external proxy
Config of the riak/riak-cs nodes appears to be all complete. I'm
encountering two issues I'd like some pointers on where to begin diagnosing
before I go around stracing everything.
Firstly:
When using s3
