3 Commits

Author	SHA1	Message	Date
mr javad seydi	7a060cab1e	feat(ilm): relocate hot objects across server pools by GET frequency ... Keep NVMe/HDD pool pairs useful without remote tiering: promote objects that are read often, demote previously moved objects once they go idle, and leave the feature off until operators set a two-pool topology. Signed-off-by: mr javad seydi <seydi.birjand@gmail.com>	2026-08-15 13:48:22 +03:30
Harshavardhana	aad50579ba	fix: wire up ILM sub-system properly for help (#19836)	2024-05-30 01:14:58 -07:00
Krishnan Parthasarathi	a7577da768	Improve expiration of tiered objects (#18926) ... - Use a shared worker pool for all ILM expiry tasks - Free version cleanup executes in a separate goroutine - Add a free version only if removing the remote object fails - Add ILM expiry metrics to the node namespace - Move tier journal tasks to expiryState - Remove unused on-disk journal for tiered objects pending deletion - Distribute expiry tasks across workers such that the expiry of versions of the same object serialized - Ability to resize worker pool without server restart - Make scaling down of expiryState workers' concurrency safe; Thanks @klauspost - Add error logs when expiryState and transition state are not initialized (yet) * metrics: Add missed tier journal entry tasks * Initialize the ILM worker pool after the object layer	2024-03-01 21:11:03 -08:00