Evening, Morning, Afternoon to All -
For today's Recap: New Python Code, a few jobs, a new release for
Ripple, and more.
(Also, no Recap coming this Friday. Unless one of you brave souls
wants to take it on, they will resume Monday.)
Enjoy -
Mark
Community Manager
Basho Technologies
wiki.basho
I was seeing some similar behavior recently on a local devrel cluster. With a
node down, introducing DELETEs into the mix seemed to cause a fair bit of
wonkiness. Especially with allow_mult=true.
I can consistently do something along these lines to reproduce at least one of
the problems I was s
Erlang: R13B04
Riak: 0.14.2
I have a three node cluster, and while one node was down, I deleted every key
in a certain bucket. Then, I started the node that was down, and it joined the
cluster.
Now, when do a listing on these keys in this bucket, and I get the entire list.
I can also get the
Hi, Keith.
It is not safe to share a single Riak client instance across multiple
client-facing threads.
Riak's conflict detection mechanisms will be misled by that sort of
sharing. Luckily, the client is quite lightweight so you shouldn't
have to worry about the cost of doing it right.
-Justin
Hi, all. Is the Ruby Riak::Client thread safe? I'm wondering if it's safe to
share a single Riak::Client instance across all threads in an application. I
might run the app in JRuby, by the way.
Are there any pros and cons to sharing a single client you can offer?
An obvious pro is that it sa
Hi Steve,
Thanks for sending over more details.
The pre- vs. post-commit hook question is a good one. The reason we chose a
pre-commit hook over a post-commit hook for Riak Search indexing is because
a post commit hook doesn't currently provide back-pressure to the Riak KV
side of the system. It
