Lecture XIII: Replication-II

Transcription

1 Lecture XIII: Replication-II CMPT 401 Summer 2007 Dr. Alexandra Fedorova

2 Outline Google File System A real replicated file system Paxos Harp A consensus algorithm used in real systems A replicated research file system 2

3 Google File System A real massive distributed file system Hundreds of servers and clients The largest cluster has >1000 storage nodes, over 300 TB of disk storage, hundreds of clients Metadata replication Data replication Design driven by application workload and technological environment Avoided many of difficulties traditionally associated with replication by designing for a specific use case 3

4 Specifics of the Google Environment FS is built of hundreds of storage machines, built of inexpensive commodity parts Component failures are a norm Application and OS bugs Human errors Hardware failures: disks, memory, network, power supplies Millions of files, each 100 MB or larger Multi-GB files are common Applications are written for GFS Allows co-design of the file system and applications 4

5 Specifics of the Google Workload Most files are mutated by appending new data large sequential writes Random writes are very uncommon Files are written once, then they are only read Reads are sequential Large streaming reads and small random reads High bandwidth is more important than low latency Google applications: Data analysis programs that scan through data repositories Data streaming applications Archiving Applications producing (intermediate) search results 5

6 GFS Architecture 6

7 GFS Architecture (cont.) Single master Multiple chunk servers Multiple clients Each is a commodity Linux machine, a server is a user-level process Files are divided into chunks Each chunk has a handle (an ID assigned by the master) Each chunk is replicated (on three machines by default) Master stores metadata, manages chunks, does garbage collection, etc. Clients communicate with master for metadata operations, but with chunkservers for data operations No additional caching (besides the Linux in-memory buffer caching) 7

8 Client/GFS Interaction Client: Takes file and offset Translates it into the chunk index within the file Sends request to master, containing file name and chunk index Master: Replies with the corresponding chunk handle and location of the replicas (the master must know where the replicas are) Client: Caches this information Contacts one of the replicas (i.e., a chunkserver) for data 8

9 Master Stores metadata The file and chunk namespaces Mapping from files to chunks Locations of each chunk s replicas Interacts with clients Creates chunk replicas Orchestrates chunk modifications across multiple replicas Ensures atomic concurrent appends Locks concurrent operations Deletes old files (via garbage collection) 9

10 Metadata On Master Metadata data aboutthe data: File names Mapping of file names to chunk IDs Chunk locations Metadata is kept in memory File names and chunk mappings are also kept persistent in an operation log Chunk locations are kept in memory only It will be lost during the crash The master asks chunk servers about their chunks at startup builds a table of chunk locations 10

11 Why Keep Metadata In Memory? To keep master operations fast Master can periodically scan its internal state in the background, in order to implement: Garbage collection Re-replication (in case of chunk server failures) Chunk migration (for load balancing) But the file system size is limited by the amount of memory on the master? This has not been a problem for GFS metadata is compact 11

12 Why Not Keep Chunk Locations Persistent? Chunk location which chunk server has a replica of a given chunk Master polls chunk servers for that information on startup Thereafter, master keeps itself up-to-date: It controls all initial chunk placement, migration and re-replication It monitors chunkserver status with regular HeartBeat messages Motivation: simplicity Eliminates the need to keep master and chunkservers synchronized Synchronization would be needed when chunkservers: Join and leave the cluster Change names Fail and restart 12

13 Operation Log Historical record of metadata changes Maintains logical order of concurrent operations Log is used for recovery the master replays it in the event of failures Master periodically checkpoints the log Checkpoint is a B-tree data structure Can be loaded into memory Used for namespace lookup without extra parsing Checkpoint can be done on the background 13

14 Data Consistency in GFS Loose data consistency applications are designed for it Applications may see inconsistentdata data is different on different replicas Applications may see data from partially completed writes undefined file region On successful modification the file region is consistent A write may leave the region undefined if the client reads the file before another client s write is complete Replicas are not guaranteed to be bytewiseidentical (we ll see why later, and how clients deal with this) 14

15 Data Consistency in GFS (cont.) Failures: A modification may fail at one or more replicas On modification failure, file region is inconsistent Successes: Modifications are applied to a chunk in the same order on all replicas After a number of successful modifications, the file region is guaranteed to be defined: All replicas have the same data All replicas contain all the data written by all the write operations 15

16 Implications of Loose Data Consistency For Applications Applications are designed to handle loose data consistency Example 1: a file is generated from beginning to end An application creates a file with a temporary name Atomically renames the file May periodically checkpoint the file while it is written File is written via appends more resilient to failures than random writes Example 2: producer-consumer file Many writers concurrently append to one file (for merged results) Each record is self-validating (contains a checksum) Client filters out padding and duplicate records 16

17 Updates of Replicated Data Each mutation (modification) is performed at all the replicas Modifications are applied in the same order across all replicas Master grants a chunk lease to one replica i.e., the primary The primary picks a serial order for all mutations to the chunk The client pushes data to all replicas The primary tells the replicas in which order they should apply modifications 17

18 Updates of Replicated Data (cont.) 1. Client asks master for replica locations 2. Master responds 3. Client pushes data to all replicas; replicas store it in a buffer cache 4. Client sends a write request to the primary (identifying the data that had been pushed) 5. Primary forwards request to the secondaries(identifies the order) 6. The secondariesrespond to the primary 7. The primary responds to the client 18

19 Failure Handling During Updates If a write fails at the primary: The primary may report failure to the client the client will retry If the primary does not respond, the client retries from Step 1 by contacting the master If a write succeeds at the primary, but fails at several replicas The client retries several times (Step 3-7) 19

20 Data Flow Data flow is decoupled from control flow Data is pushed linearly across all chunkservers in a pipelined fashion (not necessarily from client to primary and from primary to secondary) Client forwards data to the closest replica; that replica forwards to the next closest replica, etc. Pipelined fashion: while the data is incoming, the server begins forwarding it to the next replica This design ensures good network utilization 20

21 Atomic Record Appends Atomic append is a write but GFS (the primary replica) chooses the offset where the append happens; returns appends to the client This way GFS can decide on serial order of concurrent appends without client synchronization If an append fails at some replicas the client retries As a result, the file may contain multiple copies of the same record, plus replicas may be bytewise different But after a successful update all replicas will be defined they will all have the data written by the client at the same offset 21

22 Non-Identical Replicas Because of failed and retried record appends, replicas may be nonidentical bytewise Some replicas may have duplicate records (because of failed and retried appends) Some replicas may have padded file space (empty space filled with junk) if the master chooses record offset higher than the first available offset at a replica Clients must deal with it: they write self-identifying records so they can distinguish valid data from junk If the cannot tolerate duplicates, they must insert version numbers in records GFS pushes complexity to the client; without this, complex failure recovery scheme would need to be in place 22

23 Snapshot Copy of a file or a directory tree used by applications for fast copies of data sets and for checkpointing Steps involved to snapshot directory A: 1. Master revokes leases on directory A 2. Logs the operation to disk, copies metadata for A to A in its memory: both A and A point to the same files on disk 3. When a client wants to write to chunk C in A, master defers replying to the client; creates a new chunk handle C 4. Master asks each chunkserver that has replica C to create a copy in chunk C this ensures that copies are created locally, not over the network 5. All new clients modifications go to chunk C 23

24 Namespace Management and Locking Each file or directory has an associated read/write lock Each operation on a master acquires a set of read/write locks before it runs Read locks are acquired on all files/directories that are being accessed, i.e., each intermediate directory in /d1/d2/ /dn Write locks are acquired on Snapshots (to prevent creation of new files in a directory during the snapshot) File names when that file is created No write lock on directory is needed on file creation no directory inodeto modify; multiple file creations can be done concurrently 24

25 Garbage Collection File deletion is not done immediately space from deleted files is garbage collected lazily When a file is deleted the master logs the operation and renames it to a hidden name During regular metadata scan the master deletes that file s metadata (after at least three days) During regular scan of chunk namespace, the master identifies orphaned chunks, deletes that metadata Master tells chunk replicas to delete orphaned chunks 25

26 Load Balancing Goals: Maximize data availability and reliability Maximize network bandwidth utilization Google infrastructure: Cluster consists of hundreds of racks Each rack has a dozen machines Racks are connected by network switches A rack is on a single power circuit Must balance load across machines and across racks 26

27 Creation, Re-replication, Rebalancing Creation (initial replica placement): On chunk servers with low disk space utilization Limit the number of recent creations on each chunkserver recent creations mean heavy write traffic Spread replicas across racks Re-replication When the number of replicas falls below the replication target When a chunkserver becomes unavailable When a replica becomes corrupted A new replica is copied directly from an existing one Re-balancing Master periodically examines replica distribution and moves them to meet load-balancing criteria 27

28 Fault Tolerance Fast recovery No distinction between normal and abnormal shutdown Servers are routinely restarted by killing a server process Servers are designed for fast recovery all state can be recovered from the log Chunk replication Master replication Data integrity Diagnostic tools 28

29 Chunk Replication Each chunk is replicated on multiple chunkservers on different racks Users can specify different replication levels for different parts of the file namespace (default is 3) The master clones existing replicas as needed to keep each chunk fully replicated 29

30 Single Master Simplifies design Master can make sophisticated load-balancing decisions involving chunk placement using global knowledge To prevent master from becoming the bottleneck Clients communicate with master only for metadata Master keeps metadata in memory Clients cache metadata File data is transferred from chunkservers 30

31 Master Replication Master state is replicated on multiple machines, so a new server can become master if the old master fails What is replicated: operation logs and checkpoints A modification is considered successful only after it has been logged on all master replicas A single master is in charge; if it fails, it restarts almost instantaneously If a machine fails and the master cannot restart itself, a failure detector outside GFS starts a new master with a replicated operation log (no master election) Master replicas are master s shadows they operate similarly to the master w.r.t. updating the log, the in-memory metadata, polling the chunkservers 31

32 Data Integrity Disks often fail may cause data corruption Detect corrupt replicas by comparing with other chunk servers? Not a good idea divergent replicas may be legal Each chunkserver verifies its own replicas using checksums Checksums are kept in memory and stored persistently in the log Small effect on read performance checksums are kept in memory, checksum computation can be overlapped with I/O Write performance: checksum computation optimized for appends Checksum can be computed incrementally for a checksum block (64KB) If corruption is detected, the master creates new replicas using data from correct chunks During idle periods chunkservers scan inactive chunks for corruption 32

33 Detecting Stale Replicas A replica may become stale if it misses a modification while the chunkserver was down Each chunk has a version number, version numbers are used to detect stale replicas A stale replica will never be given to the client as a chunk location, and will never participate in mutation A client may read from a stale replica (because the client caches metadata) But this window is limited, because cache entries time out 33

34 Diagnostic Tools GFS servers perform diagnostic logging Helps debugging and performance analysis Diagnostic logs record: Chunk servers going up and down All RPC requests and replies RPC requests and responses from different machine logs can be collated and analyzed to determine exact interaction between machines Logs are also used for load testing and performance analysis 34

35 GFS Summary Real replicated file system Uses commodity hardware hundreds of commodity PCs and disks Two levels of replication: Metadata is replicated via replicated masters Data is replicated on replicated chunkservers Designed for specific use case for Google applications And applications are designed for GFS This is why it is simple and it actually works 35

36 GFS Summary (cont.) Design philosophy: A replicated FS can t do all things right and all things well: Strong data consistency? Identical replicas? Fast concurrent operations? That s too hard So make several operations fast, make them common case Common case operations atomic appends Client deal with weak consistency Write self-identifying records Deal with duplicate records and padding Something to learn: if generic design is hard, design for your use case that s your only hope! 36

37 Outline Google File System A real replicated file system Paxos A consensus algorithm used in real systems Used in Chubby Google s distributed lock service Why a consensus algorithm? Many replicated FS use consensus algorithms Harp A replicated research file system 37

38 The Consensus Problem A collection of processes can propose values Only a single of the proposed values must be chosen Three classes of agents: Proposers (propose the values) Acceptors (accept the values) Learners (learn the chosen values) System model Asynchronous system Failstop failures 38

39 Acceptors Naïve solution: A single acceptor Accepts the first proposed value it receives Problem: algorithm cannot terminate if the acceptor fails Let s have multiple acceptors A value is chosen if the majority of acceptors accept it We want a value to be chosen even if only one value has been proposed, so we have a requirement: P1:An acceptor must accept the first proposal that it receives 39

40 Accepting More than One Proposal P1: An acceptor must accept the first proposal that it receives There is a problem: multiple proposers propose different values each acceptor has accepted a value no single value is accepted by the majority So we must allow for acceptor to accept more than one proposal We distinguish proposals by numbers: number value n v 40

41 Choosing a Value A value is considered chosen when it has been accepted by a majority of acceptors But acceptors may accept many different proposals! We must ensure that all accepted proposals have the same value! A1 1 X A1 4 X A3 5 X 41

42 Same Value for All Proposals We must ensure that all accepted proposals have the same value! So we have another requirement: P2:If a proposal with a value v is chosen, then every highernumbered proposal issued by any proposal has value v This ensures that even if acceptors accept different proposals, the values will be the same 42

43 Same Value for All Proposals Accepted proposal numbers Accepted values A1 2 X P1 Proposal numbers Proposed values A2 1 X P2 1 X A3 1 X P3 2 X How does P3 learn X? 43

44 Learning The Right Value for Proposal A proposer decides to issue a proposal numbered n A proposer must learn the value of the highest numbered proposal less than n, such that: That proposal has been accepted in the pas, or That proposal will be accepted in the future Learning the proposals accepted thus far is easy just ask around Predicting the future (which proposals will be accepted?) is hard So the proposer controls the future! Makes the acceptors promise not to accept any proposals numbered less than n 44

45 Proposer-Acceptor Dialogue proposer Hey, what value have you accepted so far? I accepted X, with proposal #5 Ok, do me a favour, don t accept any other proposals numbered < 5. You got it! acceptor 45

46 Algorithm at the Proposer A proposer chooses request number n, sends a prepare request to some set of acceptors, asking to respond with: The highest-numbered proposal <n that it has accepted A promise to never accept another proposal numbered <n The proposer may receive responses from a majority of acceptors -it chooses the value v for its new proposal n and send it to everyone The proposer may receive responses saying that acceptors accepted no proposals -it chooses any value v and issues proposal n Once v is chosen the proposer sends an accept request with a new v 46

47 Algorithm at the Acceptor An acceptor responds to a prepare request An acceptor responds to an accept request nonly if it had not responded to a request >n Several optimizations: An acceptor does not respond to prepare request n if it has already responded to a prepare request >n (because it will not accept proposal n anyway) An acceptor ignores prepare request n if it has already accepted a proposal >n 47

48 Phase 1: The Entire Algorithm a) A proposer selects a proposal number n and sends a prepare request with number n to a majority of acceptors b) An acceptor responds to the request (unless it knows to ignore it) with: Phase 2: A promise not to accept lower-numbered request The highest-numbered request it has accepted so far a) If the proposer receives responses to its prepare request, it learns (or chooses) the right vand sends accept request to acceptors b) If an acceptor receives an accept request n it accepts the value unless it has promised to another proposer not to accept proposal with that number 48

49 Let s Play Paxos We have two proposers p1 and p2 We have k acceptors a1,, ak Each person in class is either a proposer or an acceptor; I orchestrate the actions of proposers/acceptors We will use the following notation: PR(i) prepare request for proposal i resppr(i, v) respond to PR(i) with previously accepted value v resppr(i, -) respond to PR(i) if no proposal had been accepted AR(i, v) accept request for proposal i, value v respar(i, v) respond accepting value v 49

50 Ensuring Different Proposal Numbers Each new proposal must have a different proposal number How do different proposers ensure that they do not use the same numbers? They each draw from different number sets: E.g., one uses even numbers another one odd numbers, etc. 50

51 Learning the Chosen Value Learner a process that learns which value has been chosen Whenever an acceptor accepts a value it sends a message to the learner, so the learner knows the chosen value For fault tolerance we can have multiple learners 51

52 Making Progress A scenario in which no progress is made: Proposer p1 issues proposal number n1 Proposer p2 issues proposal number n2 > n1; proposal n1 is not accepted Proposer p1 issues proposal number n3 > n2; proposal n2 is not accepted And so on The paper suggests electing a distinguished proposer this proposer sends proposals, others are silent A distinguished proposer must be elected (and we can t use Paxos) Non-distinguished proposers must know if the distinguished proposer fails (and we know how easy that is in an asynchronous system ) 52

53 PaxosImplementation Choose a distinguished proposer An acceptor records its intended response in stable storage before sending the response In case of failure the acceptor knows the value it has chosen Each proposer remembers (in stable storage) the highestnumbered proposal it has tried to issue So it does not issue different proposals with the same number 53

54 PaxosSummary Consensus algorithm that tolerates failstop failures In an asynchronous system it eventually terminates if network and process failures are repaired The algorithm proceeds in rounds, so it can tolerate acceptor and proposer failures How is it better than other consensus algorithms we studied? Non-blocking Does not rely on a single coordinator (like two-phase commit) Multiple proposers can act concurrently without violating correctness Caveat: need a distinguished leader Must be elected Must detect when it fails so we can elect a new one 54

55 Outline Google File System A real replicated file system Paxos Harp A consensus algorithm used in real systems A replicated research file system 55

56 Overview of Harp Uses primary copy replication for Reliability Availability Single primary server, backups and witness Accessed via NFS interface Performance was a concern operations log is kept in memory only: To guard against machine failures: other replicas will have the log in memory To guard against power failures: each machine has a UPS, upon power failure there is time to flush log to persistent storage 56

57 Access via NFS Interface User application OS OS NFS client NFS server Replicated FS: Primary Backup Witness 57

58 Failover Transparent to Clients User application primary OS OS NFS client NFS server Data is sent to a multicast address Reaches all potential primaries Discarded by hardware at all except the primary OS NFS server OS NFS server backup witness 58

59 Goals and Environment of Harp Provide highly available file system service via replication Assume failstop failures Survive network partitions Assume synchronous system (?) probably, because they rely on timeouts when detecting node failure In many systems, replication caused performance degradation replica communication slowed down the sending of response to the client Harp s goal was to provide reliability and availability without performance loss 59

60 Harp s Components In presence of network partitions, must have 2n + 1replicated components to survive n failures The quorum, (the majority (n+1) servers) get to form a new group and elect a new primary Usually data is replicated on 2n+1 replicas In Harp, data is replicated on n+1 servers Theother servers are used to create quorum They are called witnesses 60

61 Harp s Witness backup primary backup primary witness witness Backup and primary cannot communicate Who should be the primary? Witness resolves the tie in favor of primary Data survives at the primary Witness resolves the tie in favor of backup Data survives at the backup 61

62 Harp: Normal Operation backup primary 4. Record the operation in the in-memory log witness 1. Send request to the primary 2. Record the operation in the in-memory log 6. Commit the operation mark it as committed in memory 8. Tell the back up to commit 62

63 In-Memory Logging Client operations are recorded in the in-memory logs (at the primary and at the backup) when the response is sent to client Operations are applied to the file system later, in the background This is done to remove disk access out of critical path when communicating with the client What if there primary fails? That s okay, because in-memory log survives and the backup What if there is a power failure? The machine will operate for a while on UPS this time will be used to apply operations in the log to the file system 63

64 Write-Behind Logging Record n Record n+1 Record n+2 Record n+3 Record n+4 Record n+5 Record n+6 GLB most recently eventthat has reached the local disk at primary and backup LB most recently eventthat has reached the local disk AP most recently applied event record CP commit pointer most recently committed event record On failure the server restores the log and re-does all committed operations in the log 64

65 A Potential Failure Scenario primary backup 1. Receive operation from the client 2. Forward it to backup 3. Record the operation in the log 5. Commit the operation 4. Respond to the primary 6. Respond to the client 7. Crash Backup does not know if the operation was committed Does it assume it was not committed and discard log entries? Does it assume it committed and apply the results? 65

66 Handling Failures: View Changes View a composition of the group and the roles of the members When some members fail, the view has to change A view change selects the members of the new view and makes sure that the state of the new view reflects all committed operations form previous views The designated primary and backup monitor other group members to detect changes in communication ability If they cannot communicate with some of the members, a view change is needed Either a primary or a backup can initiate a view change (not witness) 66

67 Causes and Outcomes of View Changes A primary fails, so a new primary is needed A backup will become the primary after a view change A backup fails, someone else needs to replicate the state at the primary Witness is configured to act as a backup the witness is promoted A primary that had failed comes back It will bring itself up-to-date (using other servers logs) and will become the primary again A backup that had failed comes back It will bring itself up-to-date; the previously promoted witness will no longer act as backup the witness is demoted 67

68 View Change: The Structure The node that starts the view change acts as coordinator Phase 1: Coordinator tells others it wants to start a view change Others stop processing any operations and send the coordinator their state, i.e., log records (that the coordinator does not already have) The coordinator applies the log records to bring itself up-to-date Phase 2: The coordinator writes the new view number to disk If both backup and witness responded, witness will be demoted If only the witness responded, witness will be promoted 68

69 A Promoted Witness The witness does not have a copy of the file system state In the absence of failures the witness does not participate in the processing of file system operations If the witness is promoted, it begins participating in the processing of file system operations Two important differences: Since it has no copy of the file system, it does not apply changes to disk It never discards log records (so it can later help bring up-to-date the failed server) If the log gets large, old log entries are recorded on disk or tape When a witness is promoted it receives records of all operations that have not reached the disk at either backup or primary 69

70 Optimizations for Fast View Changes User operations are not processed during a view change, so view changes must be fast A view change may be slow if the server that must bring itself up-to-date must receive lots of log records from other servers Therefore, the server that must bring itself up-to-date in a new view (i.e., the primary that comes back after failure) brings itself up-to-date before initiating the view change If the server s disk is intact it gets log records from the witness If the disk is damaged, it get FS state from the backup and then it gets log records from the witness 70

71 Guarding Against a Killer Packet Many crashes are due to software bugs Some bugs may cause simultaneous failure at the primary and backup i.e., an OS bug is triggered by a certain FS operation To guard against this, the backup waits with applying changes to the FS until they have been applied at the primary If the primary fails after applying a certain change, the backup will likely initiate the view change and will send the log to the witness So even if the backup fails after applying the same operation that crashed the primary, the record of that operation won t be lost 71

72 Summary Primary-copy file system Unlike other replicated file system, provides good performance, because disk writes are not in the critical path Needs at least 2n+1 participants to handle n failures Data is replicated only on n+1 servers, to save disk space Wishing to have evidence/discussion on: How the system works with view changes What happens if a component crashes during a view change? What happens with log records of uncommitted operations? 72