Via the Ripple client library for Ruby, we were doing a User.find() call to
our riak cluster and received the following error:
Riak::ProtobuffsFailedRequest: Expected success from Riak but received 0.
{r_val_unsatisfied,3,0}
As a guess, we changed the read quorum to 2 from 3 and left the
write qu
+1.
Developing a comprehensive admin console would be great.
I would add merge statistics to Chad's feature requests. Would be nice to
see who how much disk space is saved during merges, which merge/threshold
triggers were hit, and possible disk usage at that time.
On Wed, Feb 6, 2013 at 2:21 P
Also: Is there an ETA on Riak Control?
On Thu, Feb 7, 2013 at 10:08 AM, Ian Ha wrote:
> +1.
>
> Developing a comprehensive admin console would be great.
>
> I would add merge statistics to Chad's feature requests. Would be nice to
> see who how much disk space is sav
Yes, you can do that on AWS.
In our case, we just defined a security group called 'riak', we set the
inbound restrictions on that group and also tell it to only accept
connections for other EC2 nodes that have the same security group. On riak
node creation, we give the 'riak' security group to th
We also run on AWS and we use security groups. You can restrict inbound
traffic to other nodes with the same security group only.
On Fri, Feb 1, 2013 at 9:32 AM, Hector Castro wrote:
> Hi,
>
> We recently published a blog post detailing methods of deployment on AWS
> [0].
>
> More specifically,
to be reported in this command.
>
> Hope this answers all your questions.
>
> Thanks!
>
>
> --
> Brian Sparrow
> Customer Service Engineer
> Basho Technologies
>
> On Friday, January 18, 2013 at 5:14 PM, Ian Ha wrote:
>
> Hi,
>
> In our production system,
Hi,
In our production system, we notice that merges are not taking place. We
have noticed, however, that when we restart riak (via a 'riak stop' then a
'riak start'), then the merges are triggered and our disk usage goes way
day (which is what we want). We use bitcask.
Why does this happen on a r
Hi,
We have a situation where our production riak cluster is missing config
information. Specifically, we are running bitcask as our backend and we did
not define an expiry_secs value, meaning data lives forever (which we don't
want).
Question: If we changed the config and define expiry_secs, does
