Hi! Cache tiering is a great solution if the cache size is larger than the hot data. Even better if the data can cool quietly in the cache. Otherwise, it’s really better not to do this. ----- Original Message -----
From: "Wido den Hollander" <wido@42on.com> To: "Eikermann, Robert" <eikermann@se-rwth.de>, ceph-users@ceph.io Sent: Monday, 16 September, 2019 12:51:45 Subject: [ceph-users] Re: Activate Cache Tier on Running Pools
On 9/16/19 11:36 AM, Eikermann, Robert wrote:
Hi,
I’m using Ceph in combination with Openstack. For the “VMs” Pool I’d like to enable writeback caching tier, like described here: [ https://docs.ceph.com/docs/luminous/rados/operations/cache-tiering/ | https://docs.ceph.com/docs/luminous/rados/operations/cache-tiering/ ] .
Can you explain why? The cache tiering has some serious flaws and can even decrease performance instead of improve it.
What are you trying to solve?
Wido
Should it be possible to do that on a running pool? I tried to do so and immediately all VMs (Linux Ubuntu OS) running on Ceph disks got readonly filesystems. No errors were shown in ceph (but also no traffic arrived after enabling the cache tier). Removing the cache tier , rebooting the VMs and doing a filesystemcheck repaired everything.
Best
Robert
_______________________________________________ ceph-users mailing list -- [ mailto:ceph-users@ceph.io | ceph-users@ceph.io ] To unsubscribe send an email to [ mailto:ceph-users-leave@ceph.io | ceph-users-leave@ceph.io ]
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io