18 Jun 2013 21:58
Re: question about riak siblings
Jeremy Ong <jeremy <at> quarkgames.com>
2013-06-18 19:58:05 GMT
2013-06-18 19:58:05 GMT
On Tue, Jun 18, 2013 at 12:57 PM, Jeremy Ong <jeremy <at> quarkgames.com> wrote:
Suppose I have two sources writing to the database, source A and source B.
Next, suppose A and B both issue a write to the database so they spawn two siblings: [a1, b1].
Finally, suppose A writes another object using the metadata of the riak object returned when writing a2. This will lead to the following situation:
Sorry typo. This should read:
"Finally, suppose A writes another object using the metadata of the riak object returned when writing a1"
[a1, b1, a2].
Upon the next read, the client will be presented with these three siblings. Is there a publicly exposed way to establish a strict ordering between a1 and a2?Thanks,
Jeremy
_______________________________________________ riak-users mailing list riak-users <at> lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
) we had a couple of 1.2.1 nodes crash when I
upgraded one of the other nodes to 1.3.1. The current theory is that I
made the mistake of installing the new Riak package on all the nodes
before starting the upgrade. When I restarted the first node it started
doing its handoff checks. The two 1.2.1 nodes that had vnode replicas of
the new 1.3.1 node tried to start their riak_core_handoff_receiver
functions. The only thing I can think of is that the 1.2.1 nodes didn't
actually have those functions in memory so went to disk to load them.
Because I'd upgraded the Riak software, but hadn't restarted it yet, it
couldn't find the module files it was expecting so it failed. That's the
theory, anyway. So, tip of the day, don't upgrade your software until
you're ready to restart it!
===
Secondly, we've noticed a significant change in our FSM times since
upgrading[2]. The red-ish lines are 95th percentile "puts" from our four
nodes. The blue-ish lines are "gets". We were averaging a stable sub-2ms
for puts before the upgrade and now we're closer to 4ms with a lot of
jitter. The gets are unchanged. Is this related to active anti-entropy?
The AAE trees have been indexed but we're still seeing that puts are slower.
===
Finally, we've started seeing the following error occasionally pop up on
various nodes:
[error] <0.212.0> Supervisor riak_pipe_fitting_sup had child undefined
started with riak_pipe_fitting:start_link() at <0.4459.767> exit with
reason noproc in context shutdown_error
According to riak_pipe issue #49 on GitHub[3] the problem has been
around since 1.1.2 but we're only seeing it since upgrading to 1.3.1. It
doesn't seem to be load related and we don't get any associated errors
in our application and it is happening less than once per day. Anything
we should be worrying about?
Thanks!
Shane.
[1]
RSS Feed