> > Fast write enabled would mean that the primary OSD sends #size copies to the > entire active set (including itself) in parallel and sends an ACK to the > client as soon as min_size ACKs have been received from the peers (including > itself). In this way, one can tolerate (size-min_size) slow(er) OSDs (slow > for whatever reason) without suffering performance penalties immediately > (only after too many requests started piling up, which will show as a slow > requests warning). >
What happens if there occurs an error on the slowest osd after the min_size ACK has already been send to the client? _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
