[
https://issues.apache.org/jira/browse/HDDS-17783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen resolved HDDS-17783.
-------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
> Abort Lifecycle task if lifecycle configuration is deleted or updated
> ---------------------------------------------------------------------
>
> Key: HDDS-17783
> URL: https://issues.apache.org/jira/browse/HDDS-17783
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sammi Chen
> Assignee: Sammi Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> Currently once a bucket's lifecycle task starts, it will read the lifecycle
> configuration, and use that for the whole task. The lifecycle change or
> deletion will only be noticed in next iterate. For a bucket with hundreds of
> millions of keys, one task can run up to many hours.
> This task aims to recheck the lifecycle configuration during the bucket scan
> internal, so that the update of lifecycle configuration can be reflected
> earlier than current.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]