m utual e xclusion c onsensus
play

(M UTUAL E XCLUSION , C ONSENSUS ) Includes material adapted from - PowerPoint PPT Presentation

D ISTRIBUTED C OORDINATION (M UTUAL E XCLUSION , C ONSENSUS ) Includes material adapted from Van Steen and Tanenbaums Distributed Systems book S URVEY F EEDBACK Breadth vs Depth Example Use Cases Project Difficulty Using cloud


  1. D ISTRIBUTED C OORDINATION (M UTUAL E XCLUSION , C ONSENSUS ) Includes material adapted from Van Steen and Tanenbaum’s Distributed Systems book

  2. S URVEY F EEDBACK • Breadth vs Depth • Example Use Cases • Project Difficulty • Using cloud trial version – hybrid + on premise VMs • Programming Language - Go Prof. Tim Wood & Prof. Roozbeh Haghnazar

  3. S CHEDULE • Remaining Topics • Midterm • Final Project Prof. Tim Wood & Prof. Roozbeh Haghnazar

  4. T HIS W EEK : D ISTRIBUTED C OORDINATION • Distributed Locking • Consensus • Elections • State Machine Replication • Blockchain Prof. Tim Wood & Prof. Roozbeh Haghnazar

  5. W HY L OCK ? Exec. Database Exec. • Locks let us protect a shared Process1 Process2 resource $500 • A database, values in shared memory, files on a shared file system, throttle $500 READ balance READ balance $500 control on a drone, etc Add $100 $600 $700 Add $200 • How to manage a lock in a distributed environment? $600 • How do locks limit scalability? $700 Prof. Tim Wood & Prof. Roozbeh Haghnazar

  6. Lock C ENTRALIZED A PPROACH Queue B • Simplest approach: put one node in charge C • Other nodes ask coordinator for each lock A • Block until they are granted the lock • Send release message when done Lock Lock • Coordinator can decide Grant what order to grant lock • Do we get: • Mutual exclusion? • Progress? B C • Resilience to failures? • Balanced load? wants lock wants lock Prof. Tim Wood & Prof. Roozbeh Haghnazar

  7. D ISTRIBUTED A PPROACH A 3 5 Lock • Use Lamport Clocks to order lock requests across nodes B C • Send Lock message with ++clock 5 15 • Wait for OKs from all nodes 5 Lock • When receiving Lock msg: A • Update clock following Lamport’s rules 16 • Send OK if not interested OK B • If I want the lock: • Send OK if request's clock is smaller than own OK B B C • Else, put request in queue 5 16 • When done with a lock: • Send OK to anybody in queue Prof. Tim Wood & Prof. Roozbeh Haghnazar

  8. D ISTRIBUTED A PPROACH A 3 15 Lock 5 Lock • Use Lamport Clocks to order lock requests across nodes 15 Lock B C • Send Lock message with ++clock 5 15 • Wait for OKs from all nodes 5 Lock • When receiving Lock msg: A • Update clock following Lamport’s rules • Send OK if not interested • If I want the lock: • Send OK if request's clock is smaller than own B C • Else, put request in queue • When done with a lock: • Send OK to anybody in queue Prof. Tim Wood & Prof. Roozbeh Haghnazar

  9. D ISTRIBUTED A PPROACH A 3 15 Lock 5 Lock • Use Lamport Clocks to order lock requests across nodes 15 Lock B C • Send Lock message with ++clock 5 15 • Wait for OKs from all nodes 5 Lock • When receiving Lock msg: A • Update clock following Lamport’s rules 16 • Send OK if not interested O OK B K C • If I want the lock: • Send OK if request's clock is smaller than own OK B B C • Else, put request in queue 16 16 • When done with a lock: Queue • Send OK to anybody in queue waiting for C 15 OK from B... Prof. Tim Wood & Prof. Roozbeh Haghnazar

  10. C OMPARISON • Messages per lock acquire and release • Centralized: • Distributed: • Delay before entry • Centralized: • Distributed: • Problems • Centralized: • Distributed: Prof. Tim Wood & Prof. Roozbeh Haghnazar

  11. C OMPARISON • Messages per lock acquire and release • Centralized: 2+1=3 • Distributed: 2(n-1) • Delay before entry Is the distributed • Centralized: 2 • Distributed: 2(n-1) in parallel approach better in • Problems any way? • Centralized: Coordinator crashes • Distributed: anybody crashes Prof. Tim Wood & Prof. Roozbeh Haghnazar

  12. D ISTRIBUTED S YSTEMS ARE H ARD • Going from centralized to distributed can be.. • Slower • If everyone needs to do more work • More error prone • 10 nodes are 10x more likely to have a failure than one • Much more complicated • If you need a complex protocol Often we need more than just • If nodes need to know about all others a way to lock a resource! Prof. Tim Wood & Prof. Roozbeh Haghnazar

  13. W HAT IS THE MEANING OF C ONSENSUS • Consensus is defined by Merriam-Webster as, • general agreement, • group solidarity of belief or sentiment. Prof. Tim Wood & Prof. Roozbeh Haghnazar

  14. W HY C ONSENSUS ? When you sent a request to a server it answers you easily • If server fails, there is no backup • If the number of requests increase What are the challenges? dramatically the server won’t be able to respond Prof. Tim Wood & Prof. Roozbeh Haghnazar

  15. W HY C ONSENSUS ? • Symmetric :- Any of the multiple servers can respond to the client and all the other servers are supposed to sync up with the server that responded to the client’s request, and • Asymmetric :- Only the elected leader server can respond to the client. All other servers then sync up with the leader server. Prof. Tim Wood & Prof. Roozbeh Haghnazar

  16. W HY C ONSENSUS ? While this creates a system that is devoid of corruption from a single source, it still creates a major problem. • How are any decisions made? • How does anything get done? Prof. Tim Wood & Prof. Roozbeh Haghnazar

  17. C ONSENSUS O BJECTIVES • Therefore, objectives of a consensus mechanism are: • Agreement seeking : A consensus mechanism should bring about as much agreement from the group as possible. • Collaborative : All the participants should aim to work together to achieve a result that puts the best interest of the group first. • Cooperative : All the participants shouldn’t put their own interests first and work as a team more than individuals. • Egalitarian : A group trying to achieve consensus should be as egalitarian as possible. What this basically means that each and every vote has equal weight. One person’s vote can’t be more important than another’s. • Inclusive : As many people as possible should be involved in the consensus process. It shouldn’t be like normal voting where people don’t really feel like voting because they believe that their vote won’t have any weight in the long run. • Participatory : The consensus mechanism should be such that everyone should actively participate in the the overall process. Prof. Tim Wood & Prof. Roozbeh Haghnazar

  18. D ISTRIBUTED A RCHITECTURES • Purely distributed / decentralized architectures are difficult to run correctly and efficiently (decentralized locking was pretty bad!) P4 P2 P4 P2 P3 P1 P3 P1 Decentralized Centralized • Can we mix the two? Prof. Tim Wood & Prof. Roozbeh Haghnazar

  19. E LECTIONS • Appoint a central coordinator • But allow them to be replaced in a safe, distributed way • Must be able to handle simultaneous elections • Reach a consistent result P8 P7 P2 • Who should win? P6 P3 P1 Prof. Tim Wood & Prof. Roozbeh Haghnazar

  20. P8 P1 B ULLY A LGORITHM E l e • The biggest (ID) wins c P7 P2 t • Any process P can initiate an election i o • P sends Election messages to all n process with higher Ids and awaits OK ! messages P6 P3 • If it receives an OK, it drops out and waits for an I won • If a process receives an Election msg, it returns an OK ... P5 P4 Prof. Tim Wood & Prof. Roozbeh Haghnazar

  21. P8 P1 B ULLY A LGORITHM • The biggest (ID) wins O P7 P2 K • Any process P can initiate an election • P sends Election messages to all process with higher Ids and awaits OK OK messages P6 P3 • If it receives an OK, it drops out and waits for an I won • If a process receives an Election msg, it returns an OK ... P5 P4 Prof. Tim Wood & Prof. Roozbeh Haghnazar

  22. P8 P1 B ULLY A LGORITHM I WON!!! The biggest (ID) wins • P7 P2 Election! Any process P can initiate an election • P sends Election messages to all process with higher Ids • and awaits OK messages If it receives an OK, it drops out and waits for an I won • If a process receives an Election msg, it returns an OK • and starts another election P6 P3 • If no OK messages, P becomes leader and sends I won to all process with lower Ids • If a process receives a I won , it treats P5 P4 sender as the leader Prof. Tim Wood & Prof. Roozbeh Haghnazar

  23. R ING A LGORITHM P8 P1 • Any other ideas? P7 P2 P6 P3 P5 P4 Prof. Tim Wood & Prof. Roozbeh Haghnazar

  24. R ING A LGORITHM P8 P1 Elect <1> • Initiator sends an Election message around the ring P7 P2 • Add your ID to the message Elect • When Initiator receives message <1,2> again, it announces the winner Elect <1,2,3> P6 P3 • What happens if multiple elections occur at the same time? Elect <1,2,3> P5 P4 Prof. Tim Wood & Prof. Roozbeh Haghnazar

  25. R ING A LGORITHM Elect <1,2,3,6,8> P8 P1 • Initiator sends an Election message Elect Elect around the ring <1,2,3,6> <1> • Add your ID to the message P7 P2 • When Initiator receives message again, it announces the winner Elect <1,2> Elect • What happens if multiple elections <1,2,3> P6 P3 occur at the same time? Elect <1,2,3> P5 P4 Prof. Tim Wood & Prof. Roozbeh Haghnazar

Recommend


More recommend