Re: bluestore write iops calculation

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

 



Any EC pool with m=1 is fragile. By default, min_size = k+1, so you'd
immediately stop IO the moment you lose a single OSD. min_size can be
lowered to k, but that can cause data loss and corruption. You should
set m=2 at a minimum. 4+2 doesn't take much more space than 4+1, and
it's far safer.

On Fri, Aug 2, 2019 at 11:21 PM <vitalif@xxxxxxxxxx> wrote:
>
> > where small means 32kb or smaller going to BlueStore, so <= 128kb
> > writes
> > from the client.
> >
> > Also: please don't do 4+1 erasure coding, see older discussions for
> > details.
>
> Can you point me to the discussion abort the problems of 4+1? It's not
> easy to google :)
>
> --
> Vitaliy Filippov
> _______________________________________________
> ceph-users mailing list
> ceph-users@xxxxxxxxxxxxxx
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



[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