distributed systems cs 15-440 synchronization – part iii lecture 10, sep 30, 2013 mohammad hammoud

29
Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Upload: oswin-jacobs

Post on 04-Jan-2016

225 views

Category:

Documents


9 download

TRANSCRIPT

Page 1: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Distributed SystemsCS 15-440

Synchronization – Part III

Lecture 10, Sep 30, 2013

Mohammad Hammoud

Page 2: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Today… Last Session:

Physical Clock Synchronization and Logical Clocks Centralized Mutual Exclusion

Today’s Session: Part I:

Mutual Exclusion (Cont’d) Election Algorithms

Part II: Consistency & Replication: Introduction

Announcements: PS1 grades are out PS2 is out. Due date: Oct 12, 2013 P2 is out. Design report due date: Oct 7, 2013 Midterm exam is on Wednesday Oct 9, 2013

Page 3: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Time SynchronizationPhysical Clock Synchronization (or, simply, Clock Synchronization)

Here, actual time on the computers are synchronized

Logical Clock SynchronizationComputers are synchronized based on the relative ordering of events

Mutual ExclusionHow to coordinate between processes that access the same resource?

Election AlgorithmsHere, a group of entities elect one entity as the coordinator for solving a problem

Where do We Stand in the Synchronization Chapter?Previous two lectures

Today’s lecture 3

Page 4: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Overview

Time SynchronizationClock Synchronization

Logical Clock Synchronization

Mutual Exclusion

Election Algorithms

4

Page 5: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Types of Distributed Mutual Exclusion

Mutual exclusion algorithms are classified into two categories

Client 1

Server

Resource

P1P1

Coordinator

C1C1

1. Permission-based ApproachesA process, which wants to access a shared resource, requests the permission from one or more coordinators

2. Token-based ApproachesEach shared resource has a token

Token is circulated among all the processes

A process can access the resource if it has the token

Request to access

Grant

Access

Server

Resource

Client 1

P1P1

Client 2

P2P2

Client 3

P3P3

Token

Access

Token

Access

Token

Access

5

Page 6: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Overview

Time SynchronizationClock Synchronization

Logical Clock Synchronization

Mutual ExclusionPermission-based Approaches

Token-based Approaches

Election Algorithms

6

Page 7: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Permission-based Approaches

There are two types of permission-based mutual exclusion algorithmsa. Centralized Algorithms (covered last lecture)

b. Decentralized Algorithms

7

Page 8: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

b. A Decentralized AlgorithmTo avoid the drawbacks of the centralized algorithm, Lin et al. [1] advocated a decentralized mutual exclusion algorithm

Assumptions:Distributed processes are in a Distributed Hash Table (DHT) based system

Each resource is replicated n timesThe ith replica of a resource rname is named as rname-i

Every replica has its own coordinator for controlling accessThe coordinator for rname-i is determined by using a hash function

Approach:Whenever a process wants to access the resource, it will have to get a majority vote from m > n/2 coordinators

If a coordinator does not want to vote for a process (because it has already voted for another process), it will send a “permission-denied” message to the process

8

Page 9: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

A Decentralized Algorithm – An Example

If n=10 and m=7, then a process needs at-least 7 votes to access the resource

9

P0P0

P1P1

rname-1C1C1

rname-2C2C2

rname-3C3C3

rname-4C4C4

rname-5C5C5

rname-6C6C6

rname-7C7C7

rname-8C8C8

rname-9C9C9

rname-10C10C10

Req

OK01234567

Access

Req

OK012

Deny

Deny

3

PiPi n = Number of votes gained= Process iCjCj = Coordinator j

rname-x xth replica = of a resource rname

Page 10: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Fault-tolerance in Decentralized Algorithm

The decentralized algorithm assumes that the coordinator recovers quickly from a failure

However, the coordinator would have reset its state after recovery

Coordinator could have forgotten any vote it had given earlier

Hence, the coordinator may incorrectly grant permission to the processes

Mutual exclusion cannot be deterministically guaranteed

But, the algorithm probabilistically guarantees mutual exclusion

10

Page 11: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Probabilistic Guarantees in the Decentralized Algorithm

11

Page 12: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Overview

Time SynchronizationClock Synchronization

Logical Clock Synchronization

Mutual ExclusionPermission-based Approaches

Token-based Approaches

Election Algorithms

12

Page 13: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

In the Token Ring algorithm, each resource is associated with a token

The token is circulated among the processes

The process with the token can access the resource

Circulating the token among processes:

A Token Ring Algorithm

13

Resource

TAccess

T

T

Page 14: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Discussion about Token Ring

14

Page 15: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Comparison of Mutual Exclusion Algorithms

Assume that:n = Number of processes in the distributed system

For the Decentralized algorithm:

m = minimum number of coordinators who have to agree for a process to access a resource

k = average number of requests made by the process to a coordinator to request for a vote

15

Algorithm

Delay before a process can access

the resource (in message times)

Number of messages required for a process to access and release the shared resource

Problems

Centralized

Decentralized

Token Ring

32 • Coordinator crashes

2mk + m; k=1,2,…2mk • Large number of messages

1 to ∞0 to (n-1)• Token may be lost• Ring can cease to

exist since processes crash

Page 16: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Overview

Time SynchronizationClock Synchronization

Logical Clock Synchronization

Mutual ExclusionPermission-based Approaches

Token-based Approaches

Election Algorithms

16

Page 17: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Election in Distributed SystemsMany distributed algorithms require one process to act as a coordinator

Typically, it does not matter which process is elected as the coordinator

17

Client 1

Server

Resource

P1P1

Coordinator

C1C1

A Centralized Mutual Exclusion Algorithm

Time server

Berkeley Clock Synchronization Algorithm

Home Node Selection in Naming

Root note selection in Multicasting

Page 18: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Election Process

Any process Pi in the DS can initiate the election algorithm that elects a new coordinator

At the termination of the election algorithm, the elected coordinator process should be unique

Every process may know the process ID of every other processes, but it does not know which processes have crashed

Generally, we require that the coordinator is the process with the largest process ID

The idea can be extended to elect best coordinatorExample: Election of a coordinator with least computational load

If the computational load of process Pi denoted by loadi, then coordinator is the process with highest 1/loadi. Ties are broken by sorting process ID.

18

Page 19: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Election Algorithms

We will study two election algorithms1. Bully Algorithm

2. Ring Algorithm

19

Page 20: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

1. Bully AlgorithmA process initiates election algorithm when it notices that the existing coordinator is not responding

Process Pi calls for an election as follows:

20

1. Pi sends an “Election” message to all processes with higher process IDs

2. When process Pj with j>i receives the message, it responds with a “Take-over” message. Pi no more contests in the election

i. Process Pj re-initiates another call for election. Steps 1 and 2 continue

3. If no one responds, Pi wins the election. Pi

sends “Coordinator” message to every process

Election

Election

Election

Take-Over

Take-over

Election

Ele

ctio

n

Election

Take-Over

Coordinator

Page 21: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

2. Ring AlgorithmThis algorithm is generally used in a ring topology

When a process Pi detects that the coordinator has crashed, it initiates an election algorithm

21

1. Pi builds an “Election” message (E), and sends it to its next node. It inserts its ID into the Election message

2. When process Pj receives the message, it appends its ID and forwards the message

i. If the next node has crashed, Pj finds the next alive node

3. When the message gets back to the process that started the election:

i. it elects process with highest ID as coordinator, and

ii. changes the message type to “Coordination” message (C) and circulates it in the ring

E: 5

E: 5,6

E: 5,6,0 E: 5,6,0,1

E: 5,6,0,1,2

E: 5,6,0,1,2,3

E: 5,6,0,1,2,3,4

C: 6

C: 6

C: 6 C: 6

C: 6

C: 6

C: 6

Page 22: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Comparison of Election Algorithms

Assume that:n = Number of processes in the distributed system

22

Algorithm

Number of Messages for

Electing a Coordinator

Problems

Bully Algorithm

Ring Algorithm

O(n2) • Large message overhead

2n • An overlay ring topology is necessary

Page 23: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Summary of Election Algorithms

Election algorithms are used for choosing a unique process that will coordinate certain activities

At the end of the election algorithm, all nodes should uniquely identify the coordinator

We studied two algorithms for electionBully algorithm

Processes communicate in a distributed manner to elect a coordinator

Ring algorithmProcesses in a ring topology circulate election messages to choose a coordinator

23

Page 24: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Election in Large-Scale Networks

Bully Algorithm and Ring Algorithm scale poorly with the size of the network

Bully Algorithm needs O(n2) messages

Ring Algorithm requires maintaining a ring topology and requires 2n messages to elect a leader

In large networks, these approaches do not scale well

We discuss a scalable election algorithm for large-scale peer-to-peer networks

24

Page 25: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Election in Large-Scale Peer-to-Peer Networks

Many P2P networks have a hierarchical architecture for balancing the advantages between centralized and distributed networks

Typically, P2P networks are neither completely unstructured nor completely centralized

Centralized networks are efficient and, they easily facilitate locating entities and data

Flat unstructured peer-to-peer networks are robust, autonomous and balances load between all peers

25

Page 26: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Super-peers

In large unstructured Peer-to-Peer Networks, the network is organized into peers and super-peers

A super-peer is an entity that does not only participate as a peer, but also carries on an additional role of acting as a leader for a set of peers

Super-peer acts as a server for a set of client peers

All communication from and to a regular peer proceeds through a super-peer

It is expected that super-peers are long-lived nodes with high-availability

26

Regular PeerSuper Peer

Super-Peer Network

Page 27: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Super-Peers – Election Requirements

In a hierarchical P2P network, several nodes have to be selected as super-peers

Traditionally, only one node is selected as a coordinator

Requirements for a node being elected as a super-peerSuper-peers should be evenly distributed across the overlay network

There should be a predefined proportion of super-peers relative to the number of regular peers

Each super-peer should not need to serve more than a fixed number of regular peers

27

Page 28: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

Election of Super-peers in a DHT-based system

28k

m

Page 29: Distributed Systems CS 15-440 Synchronization – Part III Lecture 10, Sep 30, 2013 Mohammad Hammoud

References[1] Shi-Ding Lin, Qiao Lian, Ming Chen and Zheng Zhang, “A Practical Distributed Mutual Exclusion Protocol in Dynamic Peer-to-Peer Systems”, Lecture Notes in Computer Science, 2005, Volume 3279/2005, 11-21, DOI: 10.1007/978-3-540-30183-7_2

[2] http://en.wikipedia.org/wiki/Causality

29