Re: Does "ceph df" use "bogus" copies factor instead of (k, m) for erasure coded pool?

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

 



On Sat, 13 Apr 2019 at 06:54, Paul Emmerich <paul.emmerich@xxxxxxxx> wrote:
>
> Please don't use an EC pool with 2+1, that configuration makes no sense.

That's too much of an irony given that (2, 1) is default EC profile,
described in CEPH documentation in addition.

> min_size 3 is the default for that pool, yes. That means your data
> will be unavailable if any OSD is offline.
> Reducing min_size to 2 means you are accepting writes when you cannot
> guarantee durability which will cause problems in the long run.
> See older discussions about min_size here

Well, my primary concern wasn't about min_size at all but about this: {
> > But besides that it looks like pool usage isn't calculated according
> > to EC overhead but as if it was replicated pool with size=3 as well.
}

-- 
End of message. Next message?
_______________________________________________
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