Hi All,
Just wanted to put out an observation and see if it's either just me, or
something expected.
I've begun updating our large Riak 1.4 cluster to Riak 2.0. Each cluster
has 43TB spread evenly over 32 nodes. The riak 2.0 test nodes, after
running for 14 days, have on average around 5% more d
Happy Holidays Everyone:
I'm running Riak EE 1.4.7 and I've noticed that when performing handoffs,
multiple backends on the same vNode will transfer sequentially. That is to
say, if I have backend [A] and backend [B], and I initiate some action that
triggers ownership transfer, data will be migra
or written for Yokozuna to support Riak 1.4's
> Counter Data Type. We hope (but obviously can't guarantee) to have extractors
> for all the Data Types we release with Riak 2.0.
>
> Sam
>
> --
> Sam Elliott
> Engineer
> sam.elli...@basho.com
> --
>
&g
Evening Everyone,
I’m curious if it’s possible operate against values in distributed counters via
Yokozuna. Here’s an example result I get from performing a query, but I don’t
see what field the value is getting set to. The value should be 80840.
curl
'http://localhost:8098/search/stats?rows=
> What PRs did you have in mind? I'm curious.
>
> Oh, it looks like Sam beat me to it…to elaborate on his "not idempotent"
> line, that means when riak tells you "error" for some counter increment, it
> may only be a partial failure, and re-running the operation
In the context of using distributed counters (introduced in 1.4), is it
strictly necessary to perform a read prior to issue a write for a given key? A
la, if I want to blindly increment a value by 1, regardless of what its current
value is, is it sufficient to issue the write without previously
