[
https://issues.apache.org/jira/browse/HUDI-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17458407#comment-17458407
]
sivabalan narayanan commented on HUDI-2511:
-------------------------------------------
we already have a guard to check for archival configs are not aggressive
compared to cleaner, but guess its the case when cleaner failed for some reason
and archival went onto clean up the active timeline.
Anyways, we already have a fix on this end.
[https://github.com/apache/hudi/pull/3946]
> Aggressive archival configs compared to cleaner configs make cleaning moot
> --------------------------------------------------------------------------
>
> Key: HUDI-2511
> URL: https://issues.apache.org/jira/browse/HUDI-2511
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: sivabalan narayanan
> Assignee: sivabalan narayanan
> Priority: Blocker
> Labels: sev:high, user-support-issues
>
> if hoodie.keep.max.commits <= hoodie.cleaner.commits.retained, then cleaner
> will never kick in only. Bcoz, by then archival will kick in and will move
> entries from active to archived.
> We need to revisit this and either throw exception or make cleaner also look
> into archived commits.
> Related issue: [https://github.com/apache/hudi/issues/3739]
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
