On Wed, 7 May 2014, Dan van der Ster wrote: > Hi, > > Sage Weil wrote: > > * *Primary affinity*: Ceph now has the ability to skew selection of > OSDs as the "primary" copy, which allows the read workload to be > cheaply skewed away from parts of the cluster without migrating any > data. > > > Can you please elaborate a bit on this one? I found the blueprint [1] but > still don't quite understand how it works. Does this only change the crush > calculation for reads? i.e writes still go to the usual primary, but reads > are distributed across the replicas? If so, does this change the consistency > model in any way. It basically just skews the choice of which replica is the primary. No data has to move, but the read workload and write overhead associated with being the primary (driving recovery and forwarding writes) is diverted away from the nodes whose 'affinity' is reduced from the default/baseline. sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
