Scribd
Upload
45 views

University of Gondar

The document discusses various consistency models for distributed systems, including strict, causal, and entry consistency models that are data-centric. Client-centric models discussed are monotonic reads, monotonic writes, read your writes, and writes follow reads. These models aim to maintain a consistent view for individual client processes accessing replicas from different locations without handling simultaneous updates.

Uploaded by

yonas
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
45 views

University of Gondar

The document discusses various consistency models for distributed systems, including strict, causal, and entry consistency models that are data-centric. Client-centric models discussed are monotonic reads, monotonic writes, read your writes, and writes follow reads. These models aim to maintain a consistent view for individual client processes accessing replicas from different locations without handling simultaneous updates.

Uploaded by

yonas
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

University of Gondar

College of informatics
Department of information technology
Distributed system assignment
Consistency Model
 A consistency model is contract between a distributed data store and processes, in which the
processes agree to obey certain rules in contrast the store promises to work correctly.
 A consistency model basically refers to the degree of consistency that should be maintained
for the shared memory data.
 If a system supports the stronger consistency model, then the weaker consistency model is
automatically supported but the converse is not true.
 The types of consistency models are Data-Centric and client centric consistency models.

A.Data-Centric Consistency Models


A data store may be physically distributed across multiple machines. Each process that can access
data from the store is assumed to have a local or nearby copy available of the entire store.

1.Strict Consistency model

 Any read on a data item X returns a value corresponding to the result of the most recent write
on X
 This is the strongest form of memory coherence which has the most stringent consistency
requirement.
 Strict consistency is the ideal model but it is impossible to implement in a distributed system. It
is based on absolute global time or a global agreement on commitment of changes.

Example:
Begin with:
       

Wi(x)a –write by process Pi to data item x with the value a


Ri(x)b - read by process Pi from data item x returning the
value b
        Assume:
        Time axis is drawn horizontally, with time increasing from
left to right
        Each data item is initially NIL.
 
P1 does a write to a data item x, modifying its value to a.
        Operation W1(x)a is first performed on a copy of the data store
that is local to P1, and is then propagated to the other local
copies.
P2 later reads the value NIL, and some time after that reads a (from
its local copy of the store).

NOTE: it took some time to propagate the update of x to P2, which is


perfectly acceptable.
2.Causal Consistency

 It is a weaker model than sequential consistency.


 In Casual Consistency all processes see only those memory reference operations in the
correct order that are potentially causally related.
 Memory reference operations which are not related may be seen by different processes in
different order.
 A memory reference operation is said to be casually related to another memory reference
operation if the first operation is influenced by the second operation.
 If a write(w2) operation is casually related to another write (w1) the acceptable order is (w1,
w2).

Example: 1: causal consistency


        This sequence is allowed with a causally-consistent store,
but not with a sequentially consistent store.

NOTE: The writes W2(x)b and W1(x)c are concurrent, so it is not


required that all processes see them in the same order.
 
.3 .Entry Consistency

 In entry consistency every shared data item is associated with a synchronization variable.
 In order to access consistent data, each synchronization variable must be explicitly acquired.
 Release consistency affects all shared data but entry consistency affects only those shared
data associated with a synchronization variable.

Example:         P1 does an acquire for x, changes x once, after


which it also does an acquire for y.
        Process P2 does an acquire for x but not for y, so that it
will read value a for x, but may read NIL for y.
        Because process P3 first does an acquire for y, it will read the
value b when y is released by P1.
Note: P2’s read on ‘y’ returns NIL as no locks have been requested.
 
A valid event sequence for entry consistency.

B.Client-centric model:
These consistency model do not handle simultaneous updates.
But, to maintain a consistent view for the individual client process to access different replicas from
different locations has been carried out.

1.Monotonic Reads
If a process reads the value of a data item x, any successive read
operation on x by that process will always return that same or a more
recent value.
o       Monotonic-read consistency guarantees that if a process has
seen a value of x at time t, it will never see an older version of x
at a later time.
 Example:
o       The read operations performed by a single process P at two
different local copies of the same data store.
o       Vertical axis - two different local copies of the data store are
shown - L1 and L2
o       Time is shown along the horizontal axis
o       Operations carried out by a single process P in boldface are
connected by a dashed line representing the order in which
they are carried out.
(a) A monotonic-read consistent data store.              

                   
2.Monotonic Writes
In a monotonic-write consistent store, the following condition holds:
A write operation by a process on a data item x is completed
before any successive write operation on x by the same
process.
 
Hence: A write operation on a copy of item x is performed only if that
copy has been brought up to date by means of any preceding write
operation, which may have taken place on other copies of x. If need
be, the new write must wait for old ones to finish.
 Example:
The write operations performed by a single process P at two different
local copies of the same data store.
A monotonic-write consistent data store.         

 
o  
3.Read Your Writes
      A client-centric consistency model that is closely related to
monotonic reads is as follows. A data store is said to provide read-
your-writes consistency, if the following condition holds:
The effect of a write operation by a process on data item x will
always be seen by a successive read operation on x by the
same process.
 Hence:  a write operation is always completed before a successive
read operation by the same process, no matter where that read
operation takes place.
Example:
  A data store that provides read-your-writes consistency.      

4.Writes Follow Reads


 
A data store is said to provide writes-follow-reads consistency, if the
following holds:
 A write operation by a process on a data item x following a previous
read operation on x by the same process is guaranteed to take place
on the same or a more recent value of x that was read.
 Hence: any successive write operation by a process on a data item x
will be performed on a copy of x that is up to date with the value most
recently read by that process.Example:
(a) A writes-follow-reads consistent data store.       

You might also like