Read Before Writes on Distributed Counters

Jeremiah Peschka jeremiah.peschka at
Thu Oct 17 11:21:06 EDT 2013

When you 'update' a counter, you send in an increment operation. That's
added to an internal list in Riak. The operations are then zipped up to
provide the correct counter value on read. The worst that you'll do is add
a large(ish) number of values to the op list inside Riak.

Siblings will be created, but they will not be visible to the end user who
is reading from the counter.

Check out this demo of the new counter types from Sean Cribbs:

Jeremiah Peschka - Founder, Brent Ozar Unlimited
MCITP: SQL Server 2008, MVP
Cloudera Certified Developer for Apache Hadoop

On Thu, Oct 17, 2013 at 9:55 AM, Daniil Churikov <ddosia at> wrote:

> Correct me if I wrong, but when you blindly do update without previous
> read,
> you create a sibling, which should be resolved on read. In case if you make
> a lot of increments for counter and rarely reads it will lead to siblings
> explosion.
> I am not familiar with new counters datatypes, so I am curious.
> --
> View this message in context:
> Sent from the Riak Users mailing list archive at
> _______________________________________________
> riak-users mailing list
> riak-users at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the riak-users mailing list