3 Commits

Author	SHA1	Message	Date
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
Harshavardhana	9a012a53ef	initialize the disk healer early on (#19143) ... This PR fixes a bug that perhaps has been long introduced, with no visible workarounds. In any deployment, if an entire erasure set is deleted, there is no way the cluster recovers.	2024-02-27 23:02:14 -08:00
Krishnan Parthasarathi	87cb0081ec	Retain current and upto NewerNoncurrentVersions versions (#17909) ... applyNewerNoncurrentVersionLimit method should pass along versions unaffected by NewerNoncurrentVersions rule for further ILM evaluation.	2023-08-24 09:26:29 -07:00