FWIW, totally shutting down and restarting the cluster made this go away.
I'm assuming is that the problem was either on some particular machine, or
was related to some transient condition like rebalancing, and the restart
was either unnecessary or overkill.
On Fri, Mar 11, 2011 at 9:37 AM,
I'm seeing Riak timeout consistently after 60 seconds when doing gets and
sets on particular keys (I've only tested in the REST interface). The
timeout happens inside Riak, not inside our HTTP client. It happens
regardless of whether the key already exists, and if writing, regardless of
what the
Have you guys seen the zeromq library? It's a fast, brokerless message
passing library (the sender can talk directly to the recipient, without a
message queue server in the middle). That plus protocol buffers might be an
easy way to call out to arbitrary code for mapreduce work, and you'd get the
This is due to two factors:
1) Durability. MongoDB stores writes in RAM and flushes them to disk
periodically (by default, every 60 seconds, according to this page:
http://www.mongodb.org/display/DOCS/Durability+and+Repair). This means that
its writes can seem very, very fast, but if the machine
Along these lines, are there any ideas floating around about how to speed up
the listing of keys in a bucket? For the bitcask backend, it seems like an
index of keys-by-bucket ought to be the kind of thing that could be stored
in the hints files to speed this up without affecting performance for l
Having just got back from the Lucene Revolution convention and seen several
hours of presentations that were essentially about how to configure large
distributed Lucene applications, Riak Search looks REALLY interesting. A
couple questions:
I know that in Lucene and Solr, committing many newly-in
