分布式计算chap-07v2章节.pptVIP

DISTRIBUTED SYSTEMSPrinciples and ParadigmsSecond EditionANDREW S. TANENBAUMMAARTEN VAN STEENChapter 7Consistency And Replication Reasons for Replication Data are replicated to increase the reliability of a system. Replication for performance Scaling in numbers Scaling in geographical area Caveat Gain in performance Cost of increased bandwidth for maintaining replication Data-centric Consistency Models Figure 7-1. The general organization of a logical data store, physically distributed and replicated across multiple processes. Continuous Consistency (1) Figure 7-2. An example of keeping track of consistency deviations [adapted from (Yu and Vahdat, 2002)]. Continuous Consistency (2) Figure 7-3. Choosing the appropriate granularity for a conit. (a) Two updates lead to update propagation. Continuous Consistency (3) Figure 7-3. Choosing the appropriate granularity for a conit. (b) No update propagation is needed (yet). Sequential Consistency (1) Figure 7-4. Behavior of two processes operating on the same data item. The horizontal axis is time. Sequential Consistency (2) A data store is sequentially consistent when: The result of any execution is the same as if the (read and write) operations by all processes on the data store … were executed in some sequential order and … the operations of each individual process appear … in this sequence in the order specified by its program. Sequential Consistency (3) Figure 7-5. (a) A sequentially consistent data store. (b) A data store that is not sequentially consistent. Sequential Consistency (4) Figure 7-6. Three concurrently-executing processes. Sequential Consistency (5) Figure 7-7. Four valid execution sequences for the processes of Fig. 7-6. The vertical axis is time. Causal Consistency (1) For a data store to be considered causally consistent, it is necessary that the store obeys the following condition: Writes that are potentially causally related … must be seen by all processes in the same order. Concurr