IS 651: Distributed Systems HW3

Slides:



Advertisements
Similar presentations
Time, Clocks, and the Ordering of Events in a Distributed System
Advertisements

Last Class: Clock Synchronization
Logical Clocks.
Linearizability Linearizability is a correctness criterion for concurrent object (Herlihy & Wing ACM TOPLAS 1990). It provides the illusion that each operation.
Time and synchronization (“There’s never enough time…”)
Time and Clock Primary standard = rotation of earth De facto primary standard = atomic clock (1 atomic second = 9,192,631,770 orbital transitions of Cesium.
Distributed Systems Spring 2009
CMPT 431 Dr. Alexandra Fedorova Lecture VIII: Time And Global Clocks.
CS 582 / CMPE 481 Distributed Systems
Lecture 13 Synchronization (cont). EECE 411: Design of Distributed Software Applications Logistics Last quiz Max: 69 / Median: 52 / Min: 24 In a box outside.
Time, Clocks, and the Ordering of Events in a Distributed System Leslie Lamport (1978) Presented by: Yoav Kantor.
Donghyun (David) Kim Department of Mathematics and Physics North Carolina Central University 1 Project Reference Some slides are in courtesy of Dr. Erciyes,
Consistency and Replication CSCI 4780/6780. Chapter Outline Why replication? –Relations to reliability and scalability How to maintain consistency of.
Multi-part Messages in KMIP John Leiseboer, QuintessenceLabs.
Synchronization in Distributed Systems Chapter 6.
Logical Clocks n event ordering, happened-before relation (review) n logical clocks conditions n scalar clocks condition implementation limitation n vector.
1 Causal Delivery Advanced Networks PhD. Saúl Pomares Hernández.
Reliable Communication in the Presence of Failures Based on the paper by: Kenneth Birman and Thomas A. Joseph Cesar Talledo COEN 317 Fall 05.
Logical Clocks. Topics Logical clocks Totally-Ordered Multicasting Vector timestamps.
Lamport’s Logical Clocks & Totally Ordered Multicasting.
Event Ordering Greg Bilodeau CS 5204 November 3, 2009.
CSE 486/586, Spring 2013 CSE 486/586 Distributed Systems Global States Steve Ko Computer Sciences and Engineering University at Buffalo.
Distributed Coordination. Turing Award r The Turing Award is recognized as the Nobel Prize of computing r Earlier this term the 2013 Turing Award went.
9/14/20051 Time, Clocks, and the Ordering of Events in a Distributed System by L. Lamport CS 5204 Operating Systems Vladimir Glina Fall 2005.
D u k e S y s t e m s Asynchronous Replicated State Machines (Causal Multicast and All That) Jeff Chase Duke University.
Logical Clocks. Topics Logical clocks Totally-Ordered Multicasting Vector timestamps.
CIS 720 Distributed Shared Memory. Shared Memory Shared memory programs are easier to write Multiprocessor systems Message passing systems: - no physically.
Linearizability Linearizability is a correctness criterion for concurrent object (Herlihy & Wing ACM TOPLAS 1990). It provides the illusion that each operation.
Feb 15, 2001CSCI {4,6}900: Ubiquitous Computing1 Announcements.
Linearizability Linearizability is a correctness criterion for concurrent object (Herlihy & Wing ACM TOPLAS 1990). It provides the illusion that each operation.
Logical Clocks. Topics r Logical clocks r Totally-Ordered Multicasting.
Event Ordering. CS 5204 – Operating Systems2 Time and Ordering The two critical differences between centralized and distributed systems are: absence of.
Hwajung Lee. Primary standard = rotation of earth De facto primary standard = atomic clock (1 atomic second = 9,192,631,770 orbital transitions of Cesium.
CSE 486/586 CSE 486/586 Distributed Systems Global States Steve Ko Computer Sciences and Engineering University at Buffalo.
Lecture 4-1 Computer Science 425 Distributed Systems (Fall2009) Lecture 4 Chandy-Lamport Snapshot Algorithm and Multicast Communication Reading: Section.
6.2 Logical Clocks Kranthi Koya09/23/2015. Overview Introduction Lamport’s Logical Clocks Vector Clocks Research Areas Conclusion.
Efficient Algorithms for Distributed Snapshots and Global Virtual Time Approximation Author: Friedermann Mattern Presented By: Shruthi Koundinya.
Clock Snooping and its Application in On-the-fly Data Race Detection Koen De Bosschere and Michiel Ronsse University of Ghent, Belgium Taipei, TaiwanDec.
Logical Clocks event ordering, happened-before relation (review) logical clocks conditions scalar clocks  condition  implementation  limitation vector.
Secure Causal Atomic Broadcast, Revisited
CSE 486/586 Distributed Systems Global States
Principles of Computer Security
CSC 8320 Advanced Operating System
Principles of Computer Security
Replication and Consistency
Time and Clock Primary standard = rotation of earth
Time and Clock.
COT 5611 Operating Systems Design Principles Spring 2012
Replication and Consistency
IS 651: Distributed Systems Midterm
Distributed Systems CS
Linearizability Linearizability is a correctness criterion for concurrent object (Herlihy & Wing ACM TOPLAS 1990). It provides the illusion that each operation.
Time and Clock.
Replication Improves reliability Improves availability
Outline Theoretical Foundations - continued Lab 1
Time And Global Clocks CMPT 431.
Event Ordering.
Outline Theoretical Foundations
CS 425 / ECE 428  2013, I. Gupta, K. Nahrtstedt, S. Mitra, N. Vaidya, M. T. Harandi, J. Hou.
ITEC452 Distributed Computing Lecture 10 Time in a Distributed System
Distributed Systems CS
Distributed Systems CS
Chapter 5 (through section 5.4)
Outline Theoretical Foundations - continued
Distributed Systems CS
CSE 486/586 Distributed Systems Consistency --- 1
Proof of liveness: an example
COT 5611 Operating Systems Design Principles Spring 2014
Replication and Consistency
Outline Theoretical Foundations
Presentation transcript:

IS 651: Distributed Systems HW3 Sisi Duan Assistant Professor Information Systems sduan@umbc.edu

HW3 Q1. Why E1->E10 and E8||E9? Definition (->): We define e->e’ if… Logical ordering: e->e’ if e->e’ for any process I Messages: send (m) -> receive (m) for any message m Transitivity: e->e’‘ if e->e’ and e’->e’’

HW3 Three rules: At process i, increment Li before each event To send a message m at process i, apply rule 1 and then include the current local time in the message: i.e., send(m,Li) To receive a message (m,t) at process j, set Lj = max(Lj,t) and then apply rule 1 before time-stamping the receive event Alice sends sync request to Bob Bob receives sync request from Alice Alice sends sync request to Carol Bob sends sync acknowledgment to Alice Bob sends sync request to Carol Carol receives sync request from Bob Alice receives sync acknowledgment from Bob Carol sends sync acknowledgment to Bob Carol receives sync request from Alice Bob receives sync acknowledgment from Carol Carol sends sync acknowledgment to Alice Alice receives sync acknowledgment from Carol Alice combines the results and sends the final report to Bob Alice sends final report to Carol Carol receives final report from Alice Bob receives final report from Alice

HW3 Q3.B. Sequential consistency does not admit a scalable implementation because it requires a total ordering of all operations in the system.  Q3.E. Sequential consistency is sufficient to guarantee that an airline never overbooks its seats when multiple clients reserve seats on the same airplane.

HW3 Q3.C. Obeying all causal orderings is sufficient to guarantee convergence of state maintained by multiple replicas.  Q3.D. Causal consistency is sufficient to guarantee that an airline never overbooks its seats when multiple clients reserve seats on the same airplane.  Q3.A. Sequential consistency guarantees causal ordering.  In shared memory scenario, I think it’s true. But this is not always true.

Causal order vs Total order in the broadcast scenario [Lamport, Comm. ACM 1978] [Lamport, Distrib. Comput. 1986] Causal order If the broadcast of message m1 "happens before" or "causally precedes" the broadcast of message m2, then no correct process delivers m2 before it delivers m1. m1 “Chase charges 10%!” m2 “That is outrageous!”

Causal order vs Total order in the broadcast scenario ✓ Causal order Chase: “Charge 10%” Outrageous! $100 $90 Chase: “Charge 10%” Outrageous! $100 $90 $100

Causal order vs Total order in the broadcast scenario ✘ Causal order Chase: “Charge 10%” Outrageous! $100 $100 $90 Chase: “Charge 10%” Outrageous! $100 $90 $90 $100

Causal order vs Total order in the broadcast scenario ✓ ✘ Causal order Total order Chase: “Charge 10%” Client 1: “Deposit $100” Outrageous! $100 $90 $190 Client 1: “Deposit $100” Chase: “Charge 10%” Outrageous! $100 $200 $180 $100

Causal order vs Total order in the broadcast scenario ✘ ✓ Causal order Total order Chase: “Charge 10%” Outrageous! $100 $100 $90 Chase: “Charge 10%” Outrageous! $100 $100 $90 $100

Causal order vs Total order in the broadcast scenario ✓ ✓ Causal order Total order Chase: “Charge 10%” Client 1: “Deposit $100” Outrageous! $100 $90 $190 Chase: “Charge 10%” Client 1: “Deposit $100” Outrageous! $100 $90 $190 $100