Interview Bootcamp
Vote

0% completed

​

Vector Clocks and Conflicting Data

The previous lesson showed why a sloppy quorum lets multiple conflicting values exist for the same key. Let's look at how that happens, and how Dynamo deals with it.

What is clock skew?

On a single machine, one clock is enough. Suppose a write to key k lands at wall-clock time t1. A second write to the same key lands at t2. Since t2 is greater than t1, the second write is newer, and the database can safely overwrite the first value with it.

A distributed system breaks that assumption

.....

.....

.....

Like the course? Get enrolled and start learning!
A

Amey Naik

· 5 years ago

"Server B sees a write to key k1, with value bax. It assigns it a version of [B:1]."

Show 3 replies

Reading Progress

0%

Vote for new content