Primary Copy Locking

In primary copy locking approach all locks for a data item x are requested at the site of the primary copy. We will assume the first that also all the read and write operations are performed on this copy, however writes are then propagated to all the other copies. Considering a database if we choose x1,y1,z2 as the primary copies then the availability of the database of the 12 transactions is the same as in the majority approach, because the assignment of votes which we had applied determined a primary copy situation his will always happen if we apply weighted voting to items having only two copies , However this is a particular case f many copies exist so that different majorities can be built then the two copy approach by a particular assignment of votes several enhancements of the primary copy approach exist which make it more attractive. The principle ones are 1) Allowing consistent reads at different copies than the primary even if read locks are requested only at the primary, this enhances the locality of reads 2) Allowing the migration of the primary copy of a site crash makes it unavailable, this enhances availability 3) Allowing the migration of the primary copy depending on its usage patterns, this enhances the locality aspect