[jira] [Created] (HDDS-15065) Reduce Ratis snapshot creation gap to eliminate SCM flush delay and remove redundant Ozone configuration

["Priyesh K (Jira)" <ji...@apache.org>]

Priyesh K created HDDS-15065:
--------------------------------

             Summary: Reduce Ratis snapshot creation gap to eliminate SCM flush delay and remove redundant Ozone configuration
                 Key: HDDS-15065
                 URL: https://issues.apache.org/jira/browse/HDDS-15065
             Project: Apache Ozone
          Issue Type: Bug
          Components: SCM
            Reporter: Priyesh K
            Assignee: Priyesh K


This is a follow-up to HDDS-8485.

The issue of delayed delete block processing in SCM still persists due to internal behavior in Apache Ratis.

Although a timer-based flush mechanism was introduced, its effectiveness is limited because Ratis enforces a *minimum transaction gap (1024)* before triggering certain operations such as snapshot-related checks.

*Code Reference: [RaftServerImpl (lines 1317–1320)|https://github.com/apache/ratis/blob/f141e10551a1bef69c0c7387dd184bc88e821b6d/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L1317-L1320]*

Because of this constraint, flush operations remain indirectly gated by the transaction gap, negating the intended benefit of the timer-based approach.
*Proposed Fix*
 * Reduce the value of {{ozone.scm.ha.ratis.server.snapshot.creation.gap}} from *1024 to 1*

 * Remove this configuration from Ozone to avoid duplication and rely on appropriate defaults within Ratis



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org