Re: [ceph-users] Jewel/Luminous Filestore/Bluestore for a new cluster

2018-06-06 Thread Simon Ironside
On 05/06/18 01:14, Subhachandra Chandra wrote: We have not observed any major issues. We have had occasional OSD daemon crashes due to an assert which is a known bug but the cluster recovered without any intervention each time. All the nodes have been rebooted 2-3 times due to CoreOS updates a

Re: [ceph-users] Jewel/Luminous Filestore/Bluestore for a new cluster

2018-06-04 Thread Subhachandra Chandra
We have been running a Luminous.04 + Bluestor for about 3 months in production. All the daemons run as docker containers and were installed using ceph-ansible. 540 spinning drives with journal/wal/db on the same drive spread across 9 hosts. Using librados object interface directly with steady 100MB

Re: [ceph-users] Jewel/Luminous Filestore/Bluestore for a new cluster

2018-05-30 Thread Simon Ironside
On 30/05/18 20:35, Jack wrote: Why would you deploy a Jewel cluster, which is almost 3 majors versions away ? Bluestore is also the good answer It works well, have many advantages, and is simply the future of Ceph Indeed, and normally I wouldn't even ask, but as I say there's been some comment

Re: [ceph-users] Jewel/Luminous Filestore/Bluestore for a new cluster

2018-05-30 Thread Jack
On 05/30/2018 09:20 PM, Simon Ironside wrote: > * What's the recommendation for what to deploy? > > I have a feeling the answer is going to be Luminous (as that's current > LTS) and Bluestore (since that's the default in Luminous) but several > recent threads and comments on this list make me doub

[ceph-users] Jewel/Luminous Filestore/Bluestore for a new cluster

2018-05-30 Thread Simon Ironside
Hi again, I've been happily using both Hammer and Jewel with SSD journals and spinning disk Filestore OSDs for several years now and, as per my other email, I'm about to purchase hardware to build a new (separate) production cluster. I intend to use the same mixture of SSD for journals (or DB