Hi Edgar,
I'm pleased to hear you've resolved the issue.
https://github.com/basho/riak_kv/issues/666 will track adding some
validation code to protect against similar incidents.
Jon
On Fri, Sep 20, 2013 at 8:59 AM, Edgar Veiga wrote:
> Problem solved.
>
> The n_val = "3" caused the crash! I h
I was preparing a mail making that suggestion!
All the instances in my 6 machines cluster went down because of this :S
Thanks again, keep up the good work!
On 20 September 2013 16:30, Jon Meredith wrote:
> Hi Edgar,
>
> I'm pleased to hear you've resolved the issue.
> https://github.com/basho
Problem solved.
The n_val = "3" caused the crash! I had a window of time while starting a
node to send a new PUT command and restore the correct value.
Best regards, thanks Jon
On 20 September 2013 15:42, Edgar Veiga wrote:
> Yes I did, via CURL command:
>
> curl -v -XPUT http://dat7:8098/ria
Looks like the nval is set to a binary <<"3">> rather than an integer. Have you
changed it recently and how?
On Sep 20, 2013, at 8:25 AM, Edgar Veiga wrote:
> Hello everyone,
>
> Please lend me a hand here... I'm running a riak cluster of 6 machines
> (version 1.4.1).
>
> Suddenly all the no
Hello everyone,
Please lend me a hand here... I'm running a riak cluster of 6 machines
(version 1.4.1).
Suddenly all the nodes in the cluster went down and they are refusing to go
up again. It keeps crashing all the the time, this is just a sample of what
I get when starting a node:
2013-09-20 1
Yes I did, via CURL command:
curl -v -XPUT http://dat7:8098/riak/visitors -H "Content-Type:
application/json" -d '{"props":{"n_val":"3"}}'
How can I update the n_val of an already existing bucket, while the
instance is down?
On 20 September 2013 15:32, Jon Meredith wrote:
> Looks like the nva
