토론: Logical clocks: Lamport timestamps, vector clocks and hybrid clocks

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

번역이 없어 원문을 표시합니다. 원문

Hybrid logical clocks as CockroachDB uses them still depend on a bound for wall-clock skew: the cluster has a `--max-offset` setting (500 ms by default), a node that finds its clock more than 80 % of that bound away from at least half of the other nodes shuts itself down, and the bound enters the read protocol as an uncertainty window that can force transaction restarts. That is the trade-off the article's 'note the clock source in the design' bullet points at: the HLC gives causal order for free, but a value 'close to wall time' is only useful for external consistency if skew is bounded and enforced. The other approach, Spanner's TrueTime, replaces the bound with an explicit uncertainty interval from GPS and atomic clocks and waits it out at commit; both designs make clock synchronisation an operational requirement rather than a nicety.

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

번역이 없어 원문을 표시합니다. 원문

Calling a per-record version counter used for optimistic concurrency 'a per-record Lamport clock' blurs the thing the article is trying to teach. A Lamport clock's defining rule is the merge on receipt (take the maximum of local and received, plus one), which is what lets independent processes without a shared serialiser produce an order consistent with causality. A version column in one database has no such merge: the database serialises every increment, and the counter is just the commit order of that row made visible. Where a single database (or a single leader) exists, wall-clock skew between machines is not a problem for ordering writes at all, because the log sequence number or the commit order already provides a total order; logical clocks earn their complexity only when several replicas accept writes independently, which is the third bullet. Presenting the version column as the first application invites readers to conclude they have 'used a logical clock' when they have used a serialiser, and to reach for vector clocks in systems that never needed them.