Chapter 14 Asynchronous Network Model by Mikhail Nesterenko “Distributed Algorithms” by Nancy A. Lynch.

Slides:



Advertisements
Similar presentations
Impossibility of Distributed Consensus with One Faulty Process
Advertisements

DISTRIBUTED SYSTEMS II FAULT-TOLERANT BROADCAST Prof Philippas Tsigas Distributed Computing and Systems Research Group.
Lecture 8: Asynchronous Network Algorithms
Brewer’s Conjecture and the Feasibility of Consistent, Available, Partition-Tolerant Web Services Authored by: Seth Gilbert and Nancy Lynch Presented by:
PROTOCOL VERIFICATION & PROTOCOL VALIDATION. Protocol Verification Communication Protocols should be checked for correctness, robustness and performance,
Uncoordinated Checkpointing The Global State Recording Algorithm Cristian Solano.
Chapter 15 Basic Asynchronous Network Algorithms
Distributed Computing 8. Impossibility of consensus Shmuel Zaks ©
Termination Detection of Diffusing Computations Chapter 19 Distributed Algorithms by Nancy Lynch Presented by Jamie Payton Oct. 3, 2003.
Distributed Computing 8. Impossibility of consensus Shmuel Zaks ©
Global State Collection. Global state collection Some applications - computing network topology - termination detection - deadlock detection Chandy-Lamport.
CPSC 668Set 14: Simulations1 CPSC 668 Distributed Algorithms and Systems Spring 2008 Prof. Jennifer Welch.
Distributed Systems Fall 2010 Replication Fall 20105DV0203 Outline Group communication Fault-tolerant services –Passive and active replication Highly.
© 2007 Pearson Education Inc., Upper Saddle River, NJ. All rights reserved.1 Computer Networks and Internets with Internet Applications, 4e By Douglas.
CPSC 668Set 1: Introduction1 CPSC 668 Distributed Algorithms and Systems Fall 2006 Prof. Jennifer Welch.
Causality & Global States. P1 P2 P Physical Time 4 6 Include(obj1 ) obj1.method() P2 has obj1 Causality violation occurs when order.
Ordering and Consistent Cuts Presented By Biswanath Panda.
CS 582 / CMPE 481 Distributed Systems Fault Tolerance.
Distributed systems Module 2 -Distributed algorithms Teaching unit 1 – Basic techniques Ernesto Damiani University of Bozen Lesson 3 – Distributed Systems.
Asynchronous Consensus (Some Slides borrowed from ppt on Web.(by Ken Birman) )
Impossibility of Distributed Consensus with One Faulty Process Michael J. Fischer Nancy A. Lynch Michael S. Paterson Presented by: Oren D. Rubin.
Ordering and Consistent Cuts Presented by Chi H. Ho.
Distributed Systems Tutorial 4 – Solving Consensus using Chandra-Toueg’s unreliable failure detector: A general Quorum-Based Approach.
Message Passing Systems A Formal Model. The System Topology – network (connected undirected graph) Processors (nodes) Communication channels (edges) Algorithm.
Efficient Algorithms to Implement Failure Detectors and Solve Consensus in Distributed Systems Mikel Larrea Departamento de Arquitectura y Tecnología de.
Composition Model and its code. bound:=bound+1.
Time, Clocks, and the Ordering of Events in a Distributed System Leslie Lamport (1978) Presented by: Yoav Kantor.
Chapter 8 Asynchronous System Model by Mikhail Nesterenko “Distributed Algorithms” by Nancy A. Lynch.
Message Passing Systems A Formal Model. The System Topology – network (connected undirected graph) Processors (nodes) Communication channels (edges) Algorithm.
1 A Modular Approach to Fault-Tolerant Broadcasts and Related Problems Author: Vassos Hadzilacos and Sam Toueg Distributed Systems: 526 U1580 Professor:
Lecture 2 TCP/IP Protocol Suite Reference: TCP/IP Protocol Suite, 4 th Edition (chapter 2) 1.
The Problem The Mutual exclusion problem involves the allocation of a single indivisible,nonshareable resource among n users.(U1,U2….,Un). Critical region:The.
Formal Model for Simulations Instructor: DR. Lê Anh Ngọc Presented by – Group 6: 1. Nguyễn Sơn Hùng 2. Lê Văn Hùng 3. Nguyễn Xuân Hậu 4. Nguyễn Xuân Tùng.
Modeling Process CSCE 668Set 14: Simulations 2 May be several algorithms (processes) runs on each processor to simulate the desired communication system.
Why do we need models? There are many dimensions of variability in distributed systems. Examples: interprocess communication mechanisms, failure classes,
Distributed Algorithms – 2g1513 Lecture 9 – by Ali Ghodsi Fault-Tolerance in Distributed Systems.
Modelling III: Asynchronous Shared Memory Model Chapter 9 by Nancy A. Lynch presented by Mark E. Miyashita.
Total Order Broadcast and Multicast Algorithms: Taxonomy and Survey (Paper by X. Défago, A. Schiper, and P. Urbán) ACM computing Surveys, Vol. 36,No 4,
Data Link Protocols Reliable FIFO communication using less reliable channels By Ken Schmidt.
CSCE 668 DISTRIBUTED ALGORITHMS AND SYSTEMS Spring 2014 Prof. Jennifer Welch CSCE 668 Set 1: Introduction 1.
PARTIALLY SYNCHRONOUS ALGORITHMS PRESENTED BY: BINAMRA DUTTA.
Consensus with Partial Synchrony Kevin Schaffer Chapter 25 from “Distributed Algorithms” by Nancy A. Lynch.
Types of Service. Types of service (1) A network architecture may have multiple protocols at the same layer in order to provide different types of service.
Timed I/O Automata: A Mathematical Framework for Modeling and Analyzing Real-Time Systems Frits Vaandrager, University of Nijmegen joint work with Dilsun.
6.852: Distributed Algorithms Spring, 2008 Class 13.
November NC state university Group Communication Specifications Gregory V Chockler, Idit Keidar, Roman Vitenberg Presented by – Jyothish S Varma.
Totally Ordered Broadcast in the face of Network Partitions [Keidar and Dolev,2000] INF5360 Student Presentation 4/3-08 Miran Damjanovic
D u k e S y s t e m s Asynchronous Replicated State Machines (Causal Multicast and All That) Jeff Chase Duke University.
Chap 15. Agreement. Problem Processes need to agree on a single bit No link failures A process can fail by crashing (no malicious behavior) Messages take.
Several sets of slides by Prof. Jennifer Welch will be used in this course. The slides are mostly identical to her slides, with some minor changes. Set.
Global State Collection
1 © R. Guerraoui Distributed algorithms Prof R. Guerraoui Assistant Marko Vukolic Exam: Written, Feb 5th Reference: Book - Springer.
Chapter 8 Asynchronous System Model by Mikhail Nesterenko “Distributed Algorithms” by Nancy A. Lynch.
Chapter 21 Asynchronous Network Computing with Process Failures By Sindhu Karthikeyan.
1 Fault tolerance in distributed systems n Motivation n robust and stabilizing algorithms n failure models n robust algorithms u decision problems u impossibility.
Fault-Tolerant Broadcast Terminology: broadcast(m) a process broadcasts a message to the others deliver(m) a process delivers a message to itself 1.
Fault tolerance and related issues in distributed computing Shmuel Zaks GSSI - Feb
Fault tolerance and related issues in distributed computing Shmuel Zaks GSSI - Feb
Lecture 4-1 Computer Science 425 Distributed Systems (Fall2009) Lecture 4 Chandy-Lamport Snapshot Algorithm and Multicast Communication Reading: Section.
Hwajung Lee. Some applications - computing network topology - termination detection - deadlock detection Chandy Lamport algorithm does a partial job.
Introduction to distributed systems description relation to practice variables and communication primitives instructions states, actions and programs synchrony.
1 Maximality Properties Dr. Mikhail Nesterenko Presented By Ibrahim Motiwala.
1 Fault Tolerance and Recovery Mostly taken from
Chapter 8 Fault Tolerance. Outline Introductions –Concepts –Failure models –Redundancy Process resilience –Groups and failure masking –Distributed agreement.
Distributed Systems – Paxos
Chryssis Georgiou, University of Cyprus Peter Musial, VeroModo, Inc.
Theoretical Foundations
Lecture 9: Asynchronous Network Algorithms
CSCE 668 DISTRIBUTED ALGORITHMS AND SYSTEMS
CSCE 668 DISTRIBUTED ALGORITHMS AND SYSTEMS
Presentation transcript:

Chapter 14 Asynchronous Network Model by Mikhail Nesterenko “Distributed Algorithms” by Nancy A. Lynch

Outline processes channels –reliable –with failures send/receive system broadcast system multicast system

Processes system consists of an N-node directed graph G=(V,E), each node has in-neighbors and out-neighbors a process P i is associated with every node – modeled as an arbitrary I/O automaton with the following restrictions: –a process communicates with an external user through input and output actions (“user interface”) –outputs send(m) i,j where j is an out-neighbor, inputs receive(m) j,i –faults: stopping – stop i input actions that permanently disables all tasks of P i Byzantine – replaces P i with an I/O automaton with the same external interface

Channels is associated with every directed edge of the graph external interface: send(m) i,j, receive(m) i,j channel is usually specified using mixed strategy –safety properties are given as an automaton –liveness properties – using special liveness axioms complete channel – traces of the basic automaton satisfying liveness axioms in general the channel I/O automaton can be arbitrary specific kinds of interest –reliable FIFO channel – defined in Chapter 8 (called universal reliable FIFO channel) –reliable reordering channel –channel with failures

Reliable Reordering Channel liveness defined using the following axiom If at any point in  and for any m  M we have m  in-transit, then at some later point in , a receive(m) event occurs allows delivery of all messages exactly once but does not preserve order mixed strategy –safety defined using the automaton

Channels with Failures failures considered – message loss and duplication infinite number of failures – no liveness guarantees (cf. all messages are lost) restrictions on failures –strong loss limitation – if there are infinitely many sends of a certain message then there are infinitely many receives of this message –weak loss limitation – if there are infinitely many sends then there infinitely many receives –finite duplication – each message is duplicated only finitely many times channel types –lossy FIFO channel: reliable FIFO + channel loss + one of the loss limitations –lossy reordering channel: reliable reordering + channel loss + duplication + loss and finite duplication limitations

Properties of Asynchronous Send/Receive Systems partial order defined on events: event  depends on preceding event  if  and  are on the same process  is the receive and  is the send of the same message  and  are transitively related by rules 1. and 2. 1 in the sense discussed in Chapter 8

Complexity Measures communication complexity – number of messages that was sent or received (or number of bits per message) time complexity –l – upper bond on time between successive chances for each task (of each process) to perform a step –for universal reliable FIFO channel: d – upper bound of delivery time of the oldest message sometimes – the bound on the delivery time of each message (what’s the difference?) time bound can be extended to other channel types

Broadcast Systems consists of a set of processes and a single broadcast channel processes – each process output bcast(m) and input receive(m) j,i only one type of broadcast channel is considered – universal reliable broadcast channel delivers every message to every process (including the sender) in FIFO order for each particular pair of processes –there is a separate “channel” (queue) between each pair of processes reliable broadcast system has reordering of events property similar to send/receive system complexity –communication – either number of broadcasts or receives –time – same as for send/receive systems

Multicast Systems more general than broadcast and send/receive system allows to send a (single) message to a subset of processes in the system mcast(m) i,I – send a message from process P i to a subset of processes I consists of a set of processes and a single multicast channel reliable multicast channel delivers every message to every process (including the sender) in FIFO order for each particular pair of processes (separate queue for each pair) –special case – multicast where only broadcast+point-to-point (unicast) communication allowed and FIFO preserved