Re: using secondary OSDs for reading

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

 



I have the same question about when recovery is going to happen! I think
recovering from second and third OSD can lead to not impact client IO too
when the primary OSD has another recovery ops!

On Tue, Feb 9, 2021 at 1:28 PM mj <lists@xxxxxxxxxxxxx> wrote:

> Hi,
>
> Quoting the page https://docs.ceph.com/en/latest/architecture/
>
> > location query over a chatty session. The CRUSH algorithm allows a
> > client to compute where objects should be stored, and enables the
> > client to contact the primary OSD to store or retrieve the objects.
>
> So clients contact the *primary* OSD to store/retrieve objects.
>
> Why do clients not contact secondary (or even tertiary) OSDs for reading
> data? Would that not (potentially) result in greatly improved
> performance..?
>
> I'm sure there are good reasons for the current behaviour, but it seems
> logical, since you have multiple copies of the same data, to try and use
> the nearest copy?
>
> Curious :-)
>
> MJ
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx
> To unsubscribe send an email to ceph-users-leave@xxxxxxx
>
_______________________________________________
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