Back to the original post, the important point for me is that this is not
really about riak-core, but Riak, the database.
The OP in TL;DR form:
1. A thorough report of a long lived bug in claim that means many node/ring
combos end up with multiple replicas on one physical node, silently!
2. A p
Apologies in advance if this doesn't quite submit correctly to the list.
We [bet365] are very much interested in the continued development of Riak in
its current incarnation, with Core continuing to be underpinned by distributed
Erlang. We are very keen to help to build / shape / support the com
Thanks for the writeup and detailed investigation, Martin.
We ran into these issues a few months when we expanded a 5 node cluster
into a 8 node cluster. We ended up rebuilding the cluster and writing a
small escript to verify that the generated riak ring lived up to our
requirements (which were 1
Thanks for the excellent writeup.
I have a few notes on your writeup and then a little history to help
explain the motivation for the v3 work.
The Claiming Problem
One other property of the broader claim algorithm + claimant + handoff
manager group of processes that's worth mentioning is saf
> ... before the list of Basho's Github people
> (https://github.com/orgs/basho/people) who still work at Basho is reduced to
> zero?
Just a note on that list: these are the (few) people who took the
trouble to flip the visibility of their membership in their profiles.
Github seems to have chang
Jon,
Many thanks for taking the time to look at this. You've given me lots to
think about, so I will take some time before updating my write-up to take
account of your feedback.
I need to go back and look at the safe transfers issues. I spent some time
trying to work out how the claimaint trans
I don't contribute to this list as much as I lurk in #riak (craque), but
it's really great to see this kind of community support somewhere,
especially at a large place that is heavily invested in riak itself.
I have considered posting some of the operational lessons I've learned over
the past five
