Abstract

Hybrid vector clock(s) (HVC) provide a mechanism to combine the theory and practice of distributed systems. Improving on traditional vector clock(s) (VC), HVC utilizes synchronized physical clocks to reduce the size by focusing only on causality where the physical time associated with two events is within a given uncertainty window $\epsilon$ and letting physical clock alone determine the order of events that are outside the uncertainty window. In this paper, we develop a model for determining the bounds on the size of HVC. Our model uses four parameters, $\epsilon$ : uncertainty window, $\delta$ : message delay, $\alpha$ : communication frequency and $n$ : number of nodes in the system. We derive the size of HVC in terms of a delay differential equation, and show that the size predicted by our model is almost identical to the results obtained by simulation. We also identify closed form solutions that provide tight lower and upper bounds for useful special cases. We show that for many practical applications and deployment environments in Amazon EC2, the size of HVC remains only as a couple entries and substantially less than $n$ . Finally, although the analytical results rely on a specific communication pattern they are useful in evaluating size of HVC in different communication scenarios.

Highlights

  • Work on theory of distributed systems abstract away from the wall-clock/physical-clock time and use the notion of logical clocks for ordering events in asynchronous distributed systems [12, 10, 13]

  • We presented an analytical model to compute the size of Hybrid vector clocks (HVC)

  • We presented a differential equation whose solution provides the estimated size of HVC

Read more

Summary

Introduction

Work on theory of distributed systems abstract away from the wall-clock/physical-clock time and use the notion of logical clocks for ordering events in asynchronous distributed systems [12, 10, 13]. The causality relationship captured by these logical clocks, called happened-before (hb), is defined based on passing of information, rather than passing of time.. Lamport’s logical clocks [12] (LC) prescribe a total order on the events: A hb B =⇒ lc.A < lc.B but vice a versa is not necessarily true. Vector clocks [10, 13] (VC) prescribe a partial order on the events: A hb B ⇐⇒ vc.A < vc.B and A co B ⇐⇒ (¬(vc.A < vc.B) ∧ ¬(vc.B < vc.A). Using LC or VC, it is not possible to query events in relation to physical time. For capturing hb, LC and VC assume that all communication occur

Objectives
Results
Conclusion
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call