Vector Clocks and read-only clients

9 views
Skip to first unread message

Isaac Jurado

unread,
Mar 22, 2011, 10:46:55 AM3/22/11
to project-voldemort
Hello,

I'm building a tiny C client to only do GET operations over the TCP
interface relying on server routing. I've been gathering some
information about how vector clocks are used but they seem to refer
always to write operations.

As I'm only testing the GET operation and not GET_ALL nor GET_VERSION
and I have a couple of questions:

- Will GET always return a single vector-clock/value pair? (only one
result, that is)
- In case it always returns a single value, can I trust it? (and
ignore its vector clock)
- In case multiple results may be returned, where can I read more
about the logic behind vector clocks in order to decide which value to
use?

Regards.

P.S: I don't know if this matters but I'm serializing requests using
"vp1" and the Voldemort server I'm testing is 0.80.1.
Reply all
Reply to author
Forward
0 new messages