CIS 720 Replication 1.

Slides:



Advertisements
Similar presentations
COS 461 Fall 1997 Replication u previous lectures: replication for performance u today: replication for availability and fault tolerance –availability:
Advertisements

Chapter 12 Message Ordering. Causal Ordering A single message should not be overtaken by a sequence of messages Stronger than FIFO Example of FIFO but.
Transaction Management: Concurrency Control CS634 Class 17, Apr 7, 2014 Slides based on “Database Management Systems” 3 rd ed, Ramakrishnan and Gehrke.
CS 542: Topics in Distributed Systems Diganta Goswami.
Principles of Transaction Management. Outline Transaction concepts & protocols Performance impact of concurrency control Performance tuning.
CSIS 7102 Spring 2004 Lecture 5 : Non-locking based concurrency control (and some more lock-based ones, too) Dr. King-Ip Lin.
CS6223: Distributed Systems
Linearizability Linearizability is a correctness criterion for concurrent object (Herlihy & Wing ACM TOPLAS 1990). It provides the illusion that each operation.
Sanjay Ghemawat, Howard Gobioff and Shun-Tak Leung
Failure Detection The ping-ack failure detector in a synchronous system satisfies – A: completeness – B: accuracy – C: neither – D: both.
Lock-Based Concurrency Control
Replication Management. Motivations for Replication Performance enhancement Increased availability Fault tolerance.
Distributed Systems Fall 2010 Replication Fall 20105DV0203 Outline Group communication Fault-tolerant services –Passive and active replication Highly.
CS 582 / CMPE 481 Distributed Systems
Distributed Systems Fall 2009 Replication Fall 20095DV0203 Outline Group communication Fault-tolerant services –Passive and active replication Highly.
Real-Time Distributed Databases By: Chris Scardino CSC536 Monday, May 2, 2005.
Low-Latency Multi-Datacenter Databases using Replicated Commit
6.4 Data and File Replication Gang Shen. Why replicate  Performance  Reliability  Resource sharing  Network resource saving.
Sanjay Ghemawat, Howard Gobioff, and Shun-Tak Leung Google∗
6.4 Data And File Replication Presenter : Jing He Instructor: Dr. Yanqing Zhang.
Tolerating Faults in Distributed Systems
Replication March 16, Replication What is Replication?  A technique for increasing availability, fault tolerance and sometimes, performance 
Concurrency Server accesses data on behalf of client – series of operations is a transaction – transactions are atomic Several clients may invoke transactions.
Chapter 6 Distributed File Systems Summary Bernard Chen 2007 CSc 8230.
Tanenbaum & Van Steen, Distributed Systems: Principles and Paradigms, 2e, (c) 2007 Prentice-Hall, Inc. All rights reserved Chapter 7 Consistency.
Chapter 6.5 Distributed File Systems Summary Junfei Wen Fall 2013.
IM NTU Distributed Information Systems 2004 Replication Management -- 1 Replication Management Yih-Kuen Tsay Dept. of Information Management National Taiwan.
Paxos A Consensus Algorithm for Fault Tolerant Replication.
By Shruti poundarik.  Data Objects and Files are replicated to increase system performance and availability.  Increased system performance achieved.
Transactions and Concurrency Control. Concurrent Accesses to an Object Multiple threads Atomic operations Thread communication Fairness.
Chapter 4 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University Building Dependable Distributed Systems.
Spring 2003CS 4611 Replication Outline Failure Models Mirroring Quorums.
Chapter 7: Consistency & Replication IV - REPLICATION MANAGEMENT By Jyothsna Natarajan Instructor: Prof. Yanqing Zhang Course: Advanced Operating Systems.
Hwajung Lee.  Improves reliability  Improves availability ( What good is a reliable system if it is not available?)  Replication must be transparent.
Introduction to Distributed Databases Yiwei Wu. Introduction A distributed database is a database in which portions of the database are stored on multiple.
3/6/99 1 Replication CSE Transaction Processing Philip A. Bernstein.
CSE 486/586, Spring 2012 CSE 486/586 Distributed Systems Replication Steve Ko Computer Sciences and Engineering University at Buffalo.
CIS 720 Replication. Replica Management Three Subproblems Your boss says to you, “Our system is too slow, make it faster.” You decide that replication.
EEC 688/788 Secure and Dependable Computing Lecture 9 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
Antidio Viguria Ann Krueger A Nonblocking Quorum Consensus Protocol for Replicated Data Divyakant Agrawal and Arthur J. Bernstein Paper Presentation: Dependable.
9.2 SECURE CHANNELS JEJI RAMCHAND VEDULLAPALLI. Content Introduction Authentication Message Integrity and Confidentiality Secure Group Communications.
Distributed Transactions What is a transaction? (A sequence of server operations that must be carried out atomically ) ACID properties - what are these.
Topics in Distributed Databases Database System Implementation CSE 507 Some slides adapted from Navathe et. Al and Silberchatz et. Al.
Ordering of Events in Distributed Systems UNIVERSITY of WISCONSIN-MADISON Computer Sciences Department CS 739 Distributed Systems Andrea C. Arpaci-Dusseau.
Distributed Databases – Advanced Concepts Chapter 25 in Textbook.
Alternative system models
6.4 Data and File Replication
Distributed Systems CS
Distributed Transactions and Spanner
Chapter 7: Consistency & Replication IV - REPLICATION MANAGEMENT -Sumanth Kandagatla Instructor: Prof. Yanqing Zhang Advanced Operating Systems (CSC 8320)
Implementing Consistency -- Paxos
EECS 498 Introduction to Distributed Systems Fall 2017
CSIS 7102 Spring 2004 Lecture 6: Distributed databases
Linearizability Linearizability is a correctness criterion for concurrent object (Herlihy & Wing ACM TOPLAS 1990). It provides the illusion that each operation.
Distributed Database Systems
CSE 486/586 Distributed Systems Consistency --- 1
Replication Improves reliability Improves availability
Consistency and Replication
Replication and Recovery in Distributed Systems
EEC 688/788 Secure and Dependable Computing
EEC 688/788 Secure and Dependable Computing
IS 651: Distributed Systems Fault Tolerance
Distributed Transactions
CS510 - Portland State University
DISTRIBUTED SYSTEMS Principles and Paradigms Second Edition ANDREW S
by Mikael Bjerga & Arne Lange
The SMART Way to Migrate Replicated Stateful Services
EEC 688/788 Secure and Dependable Computing
Implementing Consistency -- Paxos
Ch 6. Summary Gang Shen.
Presentation transcript:

CIS 720 Replication 1

Replica Management 2

Three Subproblems Your boss says to you, “Our system is too slow, make it faster.” You decide that replication of servers is the answer. What do you do next? What are the questions that need to be answered? Where to place servers? Where to place content? What replication algorithm to use? 3

Placing Servers Given a set of N locations, how do you place the K servers? What are the goals? What is the metric that is being optimized? One algorithm, each time you place a server, minimize the average remaining distance to clients. What is “distance”? Is “average” the right thing to minimize? What if one client accesses a lot, the other not so much. 4

One-copy equivalence Conditions to ensure one-copy equivalence: - a read and a write operation cannot happen at the same time - two write operations cannot happen at the same time 5

Quorum based protocols Each copy p has a weight weight(p) For each data item d, - read quorum r(d) - write quorum w(d) Read quorum = any set of copies whose combined weight is >= r(d) Write quorum = any set of copies whose combined weight is >= w(d) 6

A B C 3 2 2 Read quorum: 3 { (A), (B, C), (A, B), (A, C), (A,B, C) } Write quorum: 4 { (A, B), (A, C), (B, C), (A,B, C)}

To ensure one-copy equivalence, we use the following rules: r(d) + w(d) > total(d) w(d) > total(d)/2 total(d) = sum of the weights of all the replicas 8

A B C 3 2 2 Read quorum: 3 Write quorum: 4

A timestamp for each variable is maintained at each replica To write x, - lock a write quorum - let max be the largest timestamps in the quorum for x - write x with timestamp max + 1 to the quorum 10

- read data items from the read quorum To read x, - lock a read quorum - read data items from the read quorum - return the value with the largest timestamp 11

Lock granting rules Two or more read locks can be granted concurrently on a replica Two write locks or a read lock and a write lock cannot be granted at the same time. 12

Avoid deadlocks Acquire locks in the increasing order of replica ids 13

Common quorum protocols Majority consensus: weight(p) = 1; N copies r(d) = N/2 + 1; w(d) = N/2 + 1 Read one/write all weight(p) = 1 r(d) = 1; w(d) = N Write one/read all 14

Fault tolerance Majority consensus: tolerate up to N/2 failures Read one/write all writes will be blocked on any failure 15

Mesh-based quorums