Hi Sergey,
We (OpenX) have a riak_core based application that's running on a 125 node
cluster (there are also other smaller clusters). We never really tested to
see where it would fall over (and the cluster was much smaller when it
started), but I see no indicators that it will fall over when we a
I'm trying to understand when and how data handoff between nodes is
triggered in riak_core. I was under the impression that data would be
shuffled when a new node joined the cluster or an existing node left the
cluster, but maybe that's not the case? It looks like joining a cluster is
accomplished
rrent owner. This design allows handoff to
> occur both due to ring changes (join/leave) as well as for hinted
> handoff (eg. when a write destined for a node was sent to a secondary
> node during a temporary partition/downtime, and is later handed off to
> the real node).
>
> -Joe
On Tue, Jul 26, 2011 at 11:35 AM, Andrew Berman wrote:
> Thanks for the reply Bryan. This all makes sense. I am fairly new to
> Erlang and wasn't sure if using a gen_server solved some of the issues
> with connections. From what I've seen a lot of people simply make
> calls to Riak directly fr
Hi,
I've got a riak_core application based on 0.13.0 that I'm updating to
riak_core 1.0. In the process, I thought I'd try moving it from framewerk
to rebar. For my initial attempt I used the riak_core template, but when I
tried to build a release with reltool I got the following error:
[root@roc
t; are asking, but hopefully this helps you some in tracking down the issue.
> You can find more on reltool.config here
> http://www.erlang.org/doc/man/reltool.html if you haven't looked already.
>
> Best of luck,
>
> Jeff
>
>
>
> On Thu, Jan 12, 2012 at 11:45 PM, Jo
Hello,
I'd like to capture statistics on all calls to my riak_core service and the
execution time of vnode commands. I looked at folsom_metrics, but for a
service that does 10-30k QPS I'm concerned about the overhead introduced of
doing ets calls. Given that, my current plan was to create several
sho_metrics_nifs:histogram_stats(MGStat).
** exception error: bad argument
in function basho_metrics_nifs:histogram_stats/1
called as basho_metrics_nifs:histogram_stats(<<>>)
5>
It looks like storing the refs in an ets table works, so I'll try that.
Thanks,
Joel
On Tue, Dec 21, 2010 at 7:25 PM, Jeremiah Peschka <
jeremiah.pesc...@gmail.com> wrote:
> I'm interested to see how it turns out.
>
> One question: Shouldn't you be able to determine equality from the vclocks?
> Timestamps could run into issues if the clocks of different machines get out
> of sync.
