Consistency in riak/luwak
vuleetu at gmail.com
Fri Nov 11 03:48:32 EST 2011
On Tue, Nov 8, 2011 at 10:28 PM, Jeremiah Peschka <
jeremiah.peschka at gmail.com> wrote:
> A couple of things:
> I may be wrong on this (no being specifically familiar with Luwak's
> internals), but when using RIak there's no guarantee that the data is
> actually written to the node you connect to. If you connect to Node3, the
> data may be written to Node6, Node9, and Node1.
> As far as the failures, you're most likely seeing a Luwak error because
> it's still replicating data across the ring. I have no idea how you're
> actually going to get around this because the Luwak API doesn't seem to
> offer a way to tune eventual consistency and say that a read is good if
> only 1 node responds.
> The question I'd ask is "What is the likelihood that a user will
> immediately try to access an object that they have just uploaded from their
> own device?"
> Jeremiah Peschka - Founder, Brent Ozar PLF, LLC
> Microsoft SQL Server MVP
Regarding your question, the likelihook is extemely high because once we
put a file into Luwak, we fire off an event to several other connected
devices telling them to grab the file. It's part of our design goals.
After a file is put into luwak, luwak says it's done and we fire of an
event for other clients to request this information. Is there any way to
wait for the file to really be ready before we fire off this notification
to client applications to download the file?
On Tue, Nov 8, 2011 at 11:14 PM, Alexander Sicular <siculars at gmail.com>
> Build a retry into your client.
We do have a retry in the client, but having it trigger all the time is not
as efficient as we'd like.
Any further insight into this would be helpful.
> On Nov 8, 2011, at 12:11 AM, vuleetu wrote:
> > Hi, guys
> > I am using luwak as dfs, right now we have couple riak nodes like 10
> there. Here is the problem we encountered, after write file success, the
> next read operation always fail. it happens when that is a little bit big
> file size. is there any way to get rid of that. because we want the user
> can get that file which is uploaded by him real time. For example, write
> file to riak node 3 should always guarantee the next read operation on that
> file to riak node 3 should be success.
> > thanks
> > Fisher
> > _______________________________________________
> > riak-users mailing list
> > riak-users at lists.basho.com
> > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users