Random questions

siculars at gmail.com siculars at gmail.com
Mon Apr 18 18:31:48 EDT 2011

(Standard disclaimer applies, to the best of my knowledge, ymmv, bla bla)

8KB max. 

Read your writes:
Use dw param to ensure everything is persisted n times. Let your client retry if it comes back w a 404. 

Don't exist in riak. Either implement higher up the stack or use dw settings. Also, don't do use riak for applications that need locks. 

Cheers. Alexander. 
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Ben Tilly <btilly at gmail.com>
Sender: riak-users-bounces at lists.basho.com
Date: Mon, 18 Apr 2011 12:47:28 
To: <riak-users at lists.basho.com>
Subject: Random questions

The first is that I've heard that there is a limit to the size of the
headers that can be sent using the http interface and therefore the
number of links that you can use.  Is this true, and if so does anyone
know what the limit is?

My second question is this.  It seems that if accesses are configured
so that writes go to a quorum, and reads also comes from a quorum,
then once a write is reported as complete, a read is close to
guaranteed to come back with that write.  How reliable is this
behavior?  I'm sure that there are boundary cases around a machine
joining in the same window that the write/read is happening, but I'd
like to know what they are.

My third question is how bad an idea people think it is to try to get
some form of atomic behavior from Riak by locking important read/write


riak-users mailing list
riak-users at lists.basho.com

More information about the riak-users mailing list