[
https://issues.apache.org/jira/browse/HDDS-11643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923573#comment-17923573
]
Ivan Zlenko commented on HDDS-11643:
------------------------------------
[~erose] the old way to delete transaction relied on
_ozone.scm.ha.ratis.snapshot.threshold_ and not on
_ozone.scm.ha.ratis.server.snapshot.creation.gap_ .
_ozone.scm.ha.ratis.server.snapshot.creation.gap_ was specifically introduced
in HDDS-8508 .
And looking at source code for time-based flush everything is working correctly
- we still just triggering snapshot operation as soon as time comes.
> Investigate time based SCM snapshot/transaction flush not working
> -----------------------------------------------------------------
>
> Key: HDDS-11643
> URL: https://issues.apache.org/jira/browse/HDDS-11643
> Project: Apache Ozone
> Issue Type: Bug
> Components: SCM
> Reporter: Ethan Rose
> Priority: Major
>
> Per [this GitHub
> discussion|https://github.com/apache/ozone/discussions/7239#discussioncomment-11027931],
> it seems that the time based snapshot implemented in HDDS-8508 may not be
> working correctly. The observed behavior is that block deletes in SCM do not
> progress until {{ozone admin containerbalancer start}} is called. This
> coincidentally invokes a [manual buffer
> flush|https://github.com/apache/ozone/blob/bd8bb39468ed1693b94b75ef85db4710cd693618/hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/ha/StatefulServiceStateManagerImpl.java#L69],
> and only after this it is observed that deletes resume from SCM. It seems
> that the time based flush is not taking effect automatically.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
