I wanted to create a few statefull containers with mysql/postgres that did not depend on local persistant storage, so I can dynamically move them around. What about using; - a 1x replicated pool and use rbd mirror, - or having postgres use 2 1x replicated pools - or upon task launch create an lvm mirror between a ceph rbd and a local drive and use local drive as a primary access device (if that is even possible with lvm) -----Original Message----- Cc: ceph-users@xxxxxxx Subject: *****SPAM***** Re: Recommended settings for PostgreSQL Another option is to let PosgreSQL do the replication with local storage. There are great reasons for Ceph, but databases optimize for this kind of thing extremely well. With replication in hand, run snapshots to RADOS buckets for long term storage. > > Hi, > > I have an existing few RBDs. I would like to create a new RBD Image > for PostgreSQL. Do you have any suggestions for such use cases? For > example; > > Currently defaults are: > > Object size (4MB) and Stripe Unit (None) > Features: Deep flatten + Layering + Exclusive Lock + Object Map + > FastDiff > > Should I use as is or should I use 16KB of object size and different sets of features for PostgreSQL? > > Thanks, > Gencer. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |