Re: Question on RGW Lifecycle Management and Tiering Between NVMe and HDD
Hi Vishu, There is no symmetric, read-triggered promotion between two local storage classes as Casey stated. The closest mechanism RGW has today is the cloud-tier read-through path: - cloud-transition transitions objects out to an S3-compatible endpoint and leaves a stub head object behind. https://docs.ceph.com/en/tentacle/radosgw/cloud-transition/ - cloud-restore brings them back, either via an explicit RestoreObject call (temporary or permanent), or transparently on GET if the tier-config has allow_read_through=true. With read-through enabled, a regular GET on a transitioned stub triggers a restore automatically. https://docs.ceph.com/en/tentacle/radosgw/cloud-restore/ That's the closest fit for your "active again -> promote back" requirement. Which in your case would require two separate Ceph clusters configured with RGW, one with NVMe and the other with HDD. ________________________________ From: Casey Bodley via ceph-users <ceph-users@ceph.io> Sent: Wednesday, April 29, 2026 8:22 AM To: Vishnu Bhaskar <vishnukb@acceleronlabs.com> Cc: ceph-users@ceph.io <ceph-users@ceph.io> Subject: [ceph-users] Re: Question on RGW Lifecycle Management and Tiering Between NVMe and HDD On Wed, Apr 29, 2026 at 7:02 AM Vishnu Bhaskar via ceph-users <ceph-users@ceph.io> wrote:
Hi,
I have a question regarding object lifecycle management in Ceph RGW.
Is it possible to use RGW lifecycle policies to automatically move objects between different storage tiers for example, from a hot tier (NVMe) to a cold tier (HDD) based on inactivity over a period of time?
Additionally, if those objects become active again (i.e., are accessed frequently after being moved to the cold tier), is there a mechanism to automatically move them back to the original hot tier (NVMe)?
I may be misunderstanding how lifecycle management works in RGW, so please correct me if that’s the case. If this type of tiering is supported, could you point me toward the recommended approach or configuration?
s3 lifecycle rules are based on object age, which only reflects the time since last write. so i'm afraid you won't be able to transition objects based on read activity
Thanks and Regards Vishnu Bhaskar Acceleron Labs Pvt Ltd Bangalore, India _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
participants (1)
-
Matthew H