Lecture 16-A: Impossibility of Consensus

Slides:



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

CS 542: Topics in Distributed Systems Diganta Goswami.
CSE 486/586, Spring 2012 CSE 486/586 Distributed Systems Consensus Steve Ko Computer Sciences and Engineering University at Buffalo.
Distributed Computing 8. Impossibility of consensus Shmuel Zaks ©
CSE 486/586, Spring 2013 CSE 486/586 Distributed Systems Consensus Steve Ko Computer Sciences and Engineering University at Buffalo.
Announcements. Midterm Open book, open note, closed neighbor No other external sources No portable electronic devices other than medically necessary medical.
Distributed Algorithms – 2g1513 Lecture 10 – by Ali Ghodsi Fault-Tolerance in Asynchronous Networks.
CS 425 / ECE 428 Distributed Systems Fall 2014 Indranil Gupta (Indy) Lecture 13: Impossibility of Consensus All slides © IG.
Computer Science 425 Distributed Systems CS 425 / ECE 428 Consensus
Consensus Hao Li.
Distributed Computing 8. Impossibility of consensus Shmuel Zaks ©
Byzantine Generals Problem: Solution using signed messages.
Asynchronous Consensus (Some Slides borrowed from ppt on Web.(by Ken Birman) )
CPSC 668Set 9: Fault Tolerant Consensus1 CPSC 668 Distributed Algorithms and Systems Fall 2006 Prof. Jennifer Welch.
CPSC 668Set 9: Fault Tolerant Consensus1 CPSC 668 Distributed Algorithms and Systems Spring 2008 Prof. Jennifer Welch.
Impossibility of Distributed Consensus with One Faulty Process Michael J. Fischer Nancy A. Lynch Michael S. Paterson Presented by: Oren D. Rubin.
Distributed systems Module 2 -Distributed algorithms Teaching unit 1 – Basic techniques Ernesto Damiani University of Bozen Lesson 4 – Consensus and reliable.
 Idit Keidar, Principles of Reliable Distributed Systems, Technion EE, Spring Principles of Reliable Distributed Systems Lecture 6: Impossibility.
 Idit Keidar, Principles of Reliable Distributed Systems, Technion EE, Spring Principles of Reliable Distributed Systems Lecture 12: Impossibility.
CS 425 / ECE 428 Distributed Systems Fall 2014 Indranil Gupta (Indy) Lecture 19: Paxos All slides © IG.
CSE 486/586, Spring 2012 CSE 486/586 Distributed Systems Consensus Steve Ko Computer Sciences and Engineering University at Buffalo.
Distributed Consensus Reaching agreement is a fundamental problem in distributed computing. Some examples are Leader election / Mutual Exclusion Commit.
Distributed Consensus Reaching agreement is a fundamental problem in distributed computing. Some examples are Leader election / Mutual Exclusion Commit.
Lecture 8-1 Computer Science 425 Distributed Systems CS 425 / CSE 424 / ECE 428 Fall 2010 Indranil Gupta (Indy) September 16, 2010 Lecture 8 The Consensus.
CSE 486/586, Spring 2012 CSE 486/586 Distributed Systems Mutual Exclusion Steve Ko Computer Sciences and Engineering University at Buffalo.
Consensus and Its Impossibility in Asynchronous Systems.
Computer Science 425 Distributed Systems (Fall 2009) Lecture 10 The Consensus Problem Part of Section 12.5 and Paper: “Impossibility of Distributed Consensus.
CS 425/ECE 428/CSE424 Distributed Systems (Fall 2009) Lecture 9 Consensus I Section Klara Nahrstedt.
Sliding window protocol The sender continues the send action without receiving the acknowledgements of at most w messages (w > 0), w is called the window.
Hwajung Lee. Reaching agreement is a fundamental problem in distributed computing. Some examples are Leader election / Mutual Exclusion Commit or Abort.
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.
SysRép / 2.5A. SchiperEté The consensus problem.
Impossibility of Distributed Consensus with One Faulty Process By, Michael J.Fischer Nancy A. Lynch Michael S.Paterson.
1 CS 525 Advanced Distributed Systems Spring Indranil Gupta (Indy) Lecture 6 Distributed Systems Fundamentals February 4, 2010 All Slides © IG.
Alternating Bit Protocol S R ABP is a link layer protocol. Works on FIFO channels only. Guarantees reliable message delivery with a 1-bit sequence number.
Fault tolerance and related issues in distributed computing Shmuel Zaks GSSI - Feb
DISTRIBUTED ALGORITHMS Spring 2014 Prof. Jennifer Welch Set 9: Fault Tolerant Consensus 1.
CS4231 Parallel and Distributed Algorithms AY 2006/2007 Semester 2 Lecture 9 Instructor: Haifeng YU.
CSE 486/586 CSE 486/586 Distributed Systems Consensus Steve Ko Computer Sciences and Engineering University at Buffalo.
The consensus problem in distributed systems
CSE 486/586 Distributed Systems Leader Election
CS 525 Advanced Distributed Systems Spring 2013
When Is Agreement Possible
Lecture 17: Leader Election
CSCE 668 DISTRIBUTED ALGORITHMS AND SYSTEMS
Cloud Computing Concepts
CS 525 Advanced Distributed Systems Spring 2018
Alternating Bit Protocol
Distributed Consensus
Agreement Protocols CS60002: Distributed Systems
Parallel and Distributed Algorithms
Distributed Systems, Consensus and Replicated State Machines
Distributed Consensus
CS 425 / ECE 428 Distributed Systems Fall 2017 Indranil Gupta (Indy)
EEC 688/788 Secure and Dependable Computing
CSE 486/586 Distributed Systems Leader Election
Consensus, FLP, and Paxos
CSE 486/586 Distributed Systems Mutual Exclusion
EEC 688/788 Secure and Dependable Computing
CSCE 668 DISTRIBUTED ALGORITHMS AND SYSTEMS
FLP Impossibility of Consensus
EEC 688/788 Secure and Dependable Computing
EEC 688/788 Secure and Dependable Computing
EEC 688/788 Secure and Dependable Computing
EEC 688/788 Secure and Dependable Computing
Distributed systems Consensus
CSE 486/586 Distributed Systems Failure Detectors
CSE 486/586 Distributed Systems Mutual Exclusion
CSE 486/586 Distributed Systems Leader Election
CSE 486/586 Distributed Systems Consensus
Presentation transcript:

Lecture 16-A: Impossibility of Consensus CS 425 / ECE 428 Distributed Systems Fall 2017 Indranil Gupta (Indy) Oct 19, 2017 Lecture 16-A: Impossibility of Consensus All slides © IG

Give it a thought Have you ever wondered why distributed server vendors always only offer solutions that promise five-9’s reliability, seven-9’s reliability, but never 100% reliable? The fault does not lie with the companies themselves, or the worthlessness of humanity. The fault lies in the impossibility of consensus 2

What is common to all of these? A group of servers attempting: Make sure that all of them receive the same updates in the same order as each other To keep their own local lists where they know about each other, and when anyone leaves or fails, everyone is updated simultaneously Elect a leader among them, and let everyone in the group know about it To ensure mutually exclusive (one process at a time only) access to a critical resource like a file 3

What is common to all of these? A group of servers attempting: Make sure that all of them receive the same updates in the same order as each other [Reliable Multicast] To keep their own local lists where they know about each other, and when anyone leaves or fails, everyone is updated simultaneously [Membership/Failure Detection] Elect a leader among them, and let everyone in the group know about it [Leader Election] To ensure mutually exclusive (one process at a time only) access to a critical resource like a file [Mutual Exclusion] 4

So what is common? Let’s call each server a “process” (think of the daemon at each server) All of these were groups of processes attempting to coordinate with each other and reach agreement on the value of something The ordering of messages The up/down status of a suspected failed process Who the leader is Who has access to the critical resource All of these are related to the Consensus problem 5

What is Consensus? 6 Formal problem statement N processes Each process p has input variable xp : initially either 0 or 1 output variable yp : initially b (can be changed only once) Consensus problem: design a protocol so that at the end, either: All processes set their output variables to 0 (all-0’s) Or All processes set their output variables to 1 (all-1’s) 6

What is Consensus? (2) Every process contributes a value Goal is to have all processes decide same (some) value Decision once made can’t be changed There might be other constraints Validity = if everyone proposes same value, then that’s what’s decided Integrity = decided value must have been proposed by some process Non-triviality = there is at least one initial system state that leads to each of the all-0’s or all-1’s outcomes 7

Why is it Important? Many problems in distributed systems are equivalent to (or harder than) consensus! Perfect Failure Detection Leader election (select exactly one leader, and every alive process knows about it) Agreement (harder than consensus) So consensus is a very important problem, and solving it would be really useful! So, is there a solution to Consensus? 8

Two Different Models of Distributed Systems Synchronous System Model and Asynchronous System Model Synchronous Distributed System Each message is received within bounded time Drift of each process’ local clock has a known bound Each step in a process takes lb < time < ub E.g., A collection of processors connected by a communication bus, e.g., a Cray supercomputer or a multicore machine 9

Asynchronous System Model Asynchronous Distributed System No bounds on process execution The drift rate of a clock is arbitrary No bounds on message transmission delays E.g., The Internet is an asynchronous distributed system, so are ad-hoc and sensor networks This is a more general (and thus challenging) model than the synchronous system model. A protocol for an asynchronous system will also work for a synchronous system (but not vice-versa) 10

Possible or Not 11 In the synchronous system model Consensus is solvable In the asynchronous system model Consensus is impossible to solve Whatever protocol/algorithm you suggest, there is always a worst-case possible execution (with failures and message delays) that prevents the system from reaching consensus Powerful result (see the FLP proof) Subsequently, safe or probabilistic solutions have become quite popular to consensus or related problems. 11

Let’s Try to Solve Consensus! Uh, what’s the system model? (assumptions!) Synchronous system: bounds on Message delays Upper bound on clock drift rates Max time for each process step e.g., multiprocessor (common clock across processors) Processes can fail by stopping (crash-stop or crash failures) 12

Consensus in Synchronous Systems For a system with at most f processes crashing All processes are synchronized and operate in “rounds” of time. Round length >> max transmission delay. the algorithm proceeds in f+1 rounds (with timeout), using reliable communication to all members Valuesri: the set of proposed values known to pi at the beginning of round r. Round 1 Round 2 Round 3 13

Consensus in Synchronous System Possible to achieve! For a system with at most f processes crashing All processes are synchronized and operate in “rounds” of time the algorithm proceeds in f+1 rounds (with timeout), using reliable communication to all members. Round length >> max transmission delay. Valuesri: the set of proposed values known to pi at the beginning of round r. - Initially Values0i = {} ; Values1i = {vi} for round = 1 to f+1 do multicast (Values ri – Valuesr-1i) // iterate through processes, send each a message Values r+1i  Valuesri for each Vj received Values r+1i = Values r+1i  Vj end di = minimum(Values f+1i) // consistent minimum based on say, id (not minimum value) 14

Why does the Algorithm work? After f+1 rounds, all non-faulty processes would have received the same set of Values. Proof by contradiction. Assume that two non-faulty processes, say pi and pj , differ in their final set of values (i.e., after f+1 rounds) Assume that pi possesses a value v that pj does not possess. pi must have received v in the very last round Else, pi would have sent v to pj in that last round  So, in the last round: a third process, pk, must have sent v to pi, but then crashed before sending v to pj.  Similarly, a fourth process sending v in the last-but-one round must have crashed; otherwise, both pk and pj should have received v.  Proceeding in this way, we infer at least one (unique) crash in each of the preceding rounds.  This means a total of f+1 crashes, while we have assumed at most f crashes can occur => contradiction. 15

Consensus in an Asynchronous System Impossible to achieve! Proved in a now-famous result by Fischer, Lynch and Patterson, 1983 (FLP) Stopped many distributed system designers dead in their tracks A lot of claims of “reliability” vanished overnight 16

Recall Asynchronous system: All message delays and processing delays can be arbitrarily long or short. Consensus: Each process p has a state program counter, registers, stack, local variables input register xp : initially either 0 or 1 output register yp : initially b (undecided) Consensus Problem: design a protocol so that either all processes set their output variables to 0 (all-0’s) Or all processes set their output variables to 1 (all-1’s) Non-triviality: at least one initial system state leads to each of the above two outcomes 17

Proof Setup For impossibility proof, OK to consider more restrictive system model, and easier problem Why is this is ok? 18

Network Global Message Buffer 19 p p’ send(p’,m) receive(p’) may return null Global Message Buffer “Network” 19

States State of a process Configuration=global state. Collection of states, one for each process; alongside state of the global buffer. Each Event (different from Lamport events) is atomic and consists of three steps receipt of a message by a process (say p) processing of message (may change recipient’s state) sending out of all necessary messages by p Schedule: sequence of events 20

C C C’ C’’ C’’ 21 Configuration C Event e’=(p’,m’) Schedule s=(e’,e’’) Equivalent 21

Lemma 1 s1 and s2 involve disjoint sets of receiving processes, Disjoint schedules are commutative C s2 Schedule s1 C’ s1 and s2 involve disjoint sets of receiving processes, and are each applicable on C Schedule s2 s1 C’’ 22

Easier Consensus Problem Easier Consensus Problem: some process eventually sets yp to be 0 or 1 Only one process crashes – we’re free to choose which one 23

Easier Consensus Problem Let config. C have a set of decision values V reachable from it If |V| = 2, config. C is bivalent If |V| = 1, config. C is 0-valent or 1-valent, as is the case Bivalent means outcome is unpredictable 24

What the FLP proof shows There exists an initial configuration that is bivalent Starting from a bivalent config., there is always another bivalent config. that is reachable 25

Lemma 2 Some initial configuration is bivalent 26 Suppose all initial configurations were either 0-valent or 1-valent. If there are N processes, there are 2N possible initial configurations Place all configurations side-by-side (in a lattice), where adjacent configurations differ in initial xp value for exactly one process. 1 1 0 1 0 1 There has to be some adjacent pair of 1-valent and 0-valent configs. 26

Lemma 2 Some initial configuration is bivalent There has to be some adjacent pair of 1-valent and 0-valent configs. Let the process p, that has a different state across these two configs., be the process that has crashed (i.e., is silent throughout) Both initial configs. will lead to the same config. for the same sequence of events Therefore, both these initial configs. are bivalent when there is such a failure 1 1 0 1 0 1 27

What we’ll show There exists an initial configuration that is bivalent Starting from a bivalent config., there is always another bivalent config. that is reachable 28

Lemma 3 Starting from a bivalent config., there is always another bivalent config. that is reachable 29

Lemma 3 Let C be the set of configs. reachable without applying e 30 A bivalent initial config. let e=(p,m) be some event applicable to the initial config. Let C be the set of configs. reachable without applying e 30

Lemma 3 Let C be the set of configs. reachable without applying e 31 A bivalent initial config. let e=(p,m) be some event applicable to the initial config. Let C be the set of configs. reachable without applying e e e e e e Let D be the set of configs. obtained by applying e to some config. in C 31

Lemma 3 D C e e e e e bivalent [don’t apply event e=(p,m)] 32

Claim. Set D contains a bivalent config. Proof. By contradiction. That is, suppose D has only 0- and 1- valent states (and no bivalent ones) There are states D0 and D1 in D, and C0 and C1 in C such that D0 is 0-valent, D1 is 1-valent D0=C0 foll. by e=(p,m) D1=C1 foll. by e=(p,m) And C1 = C0 followed by some event e’=(p’,m’) (why?) D C e e e e e bivalent [don’t apply event e=(p,m)] 33

C C0 Proof. (contd.) Case I: p’ is not p Case II: p’ same as p D0 C1 Why? (Lemma 1) But D0 is then bivalent! D C e e e e e bivalent [don’t apply event e=(p,m)] 34

But A is then bivalent! C0 Proof. (contd.) Case I: p’ is not p C1 Case II: p’ same as p e’ e C1 e D0 sch. s D1 sch. s sch. s A e D C e e e e e bivalent [don’t apply event e=(p,m)] (e’,e) E1 E0 sch. s finite deciding run from C0 p takes no steps But A is then bivalent! 35

Lemma 3 Starting from a bivalent config., there is always another bivalent config. that is reachable 36

Putting it all Together Lemma 2: There exists an initial configuration that is bivalent Lemma 3: Starting from a bivalent config., there is always another bivalent config. that is reachable Theorem (Impossibility of Consensus): There is always a run of events in an asynchronous distributed system such that the group of processes never reach consensus (i.e., stays bivalent all the time) 37

Summary Consensus Problem Agreement in distributed systems Solution exists in synchronous system model (e.g., supercomputer) Impossible to solve in an asynchronous system (e.g., Internet, Web) Key idea: with even one (adversarial) crash-stop process failure, there are always sequences of events for the system to decide any which way Holds true regardless of whatever algorithm you choose! FLP impossibility proof One of the most fundamental results in distributed systems 38

Announcements 39 Midterm Statistics min, max, mean, median, stdev On campus UG: 42 100 82.63 85 11.27 On campus Grads: 54 99 88.26 91 9.21 MCS-DS: 47 98 80.16 82 13.11 Survey: Most felt it was Alright-Difficult. Last year’s (Fall 2016) survey had identical results, so midterm was no harder than last year. MP3, HW3 out today Start early! 39

Collect your midters Three piles (Your left) (Middle) (Your Right) A-H I-P Q-Z 40