How Ceph cleans stale object on primary OSD failure?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi everyone, I'm studying Ceph replication and peering and have a doubt in
how Ceph handles cleaning of stale objects on primary OSD failure.

Scenario:

Consider a placement group: PG1, whose acting set is [A, B, C] and A is the
primary.

t1: Client writes an object to A
t2: A initiates local write
t3: A sends replication request to B
t4: A sends replication request to C
t5: A completes local write
t6: A gets replication response from B
t7: A gets replication response from C
t8: A is crashed and haven't sent acknowledgement to the client

In case if A never comes back, the object written in B and C would be stale
as it is not acknowledged to the client. How does Ceph cleans this stale
object?

Also, it would be helpful if you can share any documentation or articles
explaining Ceph replication and peering in low-level.

Regards,
Vigneshwar.
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux