PG peering
Client write and read requests issued against RADOS objects from a client are sent to the PG to which the object belongs before being persisted to OSDs. If the replication factor (denoted by the size attribute) of the pool is greater than 1, then writes must be persisted on multiple OSDs. For example, if the size of a pool is 3, then we have three copies of each Object present in the pool spread across 3 disjoint OSDs. Any write issued by a client however must to be completed on all three OSDs before the client gets an acknowledgement. Every PG denotes one OSD designated as the primary (or lead) OSD. All additional OSDs that hold a given PG are known as secondary OSDs within the context of that PG. The primary OSD is responsible ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access