[ceph-users] Re: How to identify the index pool real usage?

Yes that's right. Test them on a single OSD, to validate. Does your platform write a lot and everywhere? From what I just saw, it seems to me that the discard only applies to transactions (and not the entire disk). If you can report back the results, that would be great. __

[ceph-users] Re: How to identify the index pool real usage?

These values shouldn't be true to be able to do triming? "bdev_async_discard": "false", "bdev_enable_discard": "false", Istvan Szabo Staff Infrastructure Engineer --- Agoda Services Co., Ltd. e: istvan.sz...@agoda.com

[ceph-users] Re: How to identify the index pool real usage?

Hi, A flash system needs free space to work efficiently. Hence my hypothesis that fully allocated disks need to be notified of free blocks (trim) Cordialement, *David CASIER* Le

[ceph-users] Re: How to identify the index pool real usage?

With the nodes that has some free space on that namespace, we don't have issue, only with this which is weird. From: Anthony D'Atri Sent: Friday, December 1, 2023 10:53 PM To: David C. Cc: Szabo, Istvan (Agoda) ; Ceph Users Subject: Re: [ceph-users] How to iden

[ceph-users] Re: How to identify the index pool real usage?

>> >> Today we had a big issue with slow ops on the nvme drives which holding >> the index pool. >> >> Why the nvme shows full if on ceph is barely utilized? Which one I should >> belive? >> >> When I check the ceph osd df it shows 10% usage of the osds (1x 2TB nvme >> drive has 4x osds on it):

[ceph-users] Re: How to identify the index pool real usage?

Hi, It looks like a trim/discard problem. I would try my luck by activating the discard on a disk, to validate. I have no feedback on the reliability of the bdev_*_discard parameters. Maybe dig a little deeper into the subject or if anyone has any feedback... ___