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.
Cheers, Dan
[1]
http://wiki.ceph.com/Planning/Blueprints/Firefly/osdmap%3A_primary_role_affinity
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
