Matthew,
That's very helpful, thank you! I agree, the ring size change is probably
the most significant factor, and we probably should not have done that on
this cluster considering it is the smallest of our production clusters and
the growth rate is very low.
Daniel
On Tue, May 2, 2017 at 11:01
Hi!
I set up a new RiakTS cluster and decided to seed it with the data from my
experimental cluster by following the currently recommended backup
procedure (
http://docs.basho.com/riak/kv/2.1.4/using/cluster-operations/backing-up/)
and then restoring it using these instructions:
http://docs.basho.
Daniel,
1G of ram is an interesting and untested challenge. Others have succeeded in
getting regular Riak KV to operate on a Raspberry PI with 2g of Ram.
Here are the 3 things you can do in an attempt to drive down required RAM (in
order of priority):
1. reduce the ring size: in riak.conf s
In addition, the correct field name should be "email", not name.
http://docs.basho.com/riak/cs/2.1.1/cookbooks/configuration/riak-cs/#specifying-the-admin-user
On Tue, May 2, 2017 at 6:01 AM, Luke Bakken wrote:
> Hi Henry,
>
> In the JSON you provided, "name" is followed by a semicolon. Is this
Hi Henry,
In the JSON you provided, "name" is followed by a semicolon. Is this a
typo? If not, that could be the cause of the error.
--
Luke Bakken
Engineer
lbak...@basho.com
On Mon, May 1, 2017 at 10:26 AM, Henry- Norbert Cocos
wrote:
> Hello,
>
>
> I'm trying to run Riak CS on a RPI 3. I got
On 30 April 2017 at 13:06, Prakash Parmar
wrote:
> Hi Magnus,
>
> Thanks for your quick response.
>
> One more question. How I can get Cluster Status ?
>
> Regards,
> Prakash Parmar
>
>
Hi Prakash,
The command 'riak-admin cluster status' does not have an equivalent access
via HTTP. Like most sub
Due to the nature of what I would like my bucket to look like. I have a
string, tdate and another string 'field'. Basically it will have a {id,
token, expiry}
Is it possible to include the tdate field within a CRDT map? If not, how
then should I model my bucket and what are the implications of not