You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2025/05/29 21:31:00 UTC

[jira] [Updated] (HDDS-12819) Auto-compact tables which can tend to be large in size at intervals

     [ https://issues.apache.org/jira/browse/HDDS-12819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wei-Chiu Chuang updated HDDS-12819:
-----------------------------------
    Release Note: 
Adding a set of configuration properties.

ozone.compaction.service.enabled = false by default. Enable or disable a background job that periodically compacts rocksdb tables flagged for compaction.

ozone.om.compaction.service.run.interval = 6h by default. A background job that periodically compacts rocksdb tables flagged for compaction.
      Unit could be defined with postfix (ns,ms,s,m,h,d)

ozone.om.compaction.service.timeout = 10m by default. A timeout value of compaction service. If this is set
      greater than 0, the service will stop waiting for compaction
      completion after this time.
      Unit could be defined with postfix (ns,ms,s,m,h,d)

ozone.om.compaction.service.columnfamilies = keyTable,fileTable,directoryTable,deletedTable,deletedDirectoryTable,multipartInfoTable by default. A comma separated, no spaces list of all the column families
      that are compacted by the compaction service.
      If this is empty, no column families are compacted.

> Auto-compact tables which can tend to be large in size at intervals
> -------------------------------------------------------------------
>
>                 Key: HDDS-12819
>                 URL: https://issues.apache.org/jira/browse/HDDS-12819
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Tejaskriya Madhan
>            Assignee: Tejaskriya Madhan
>            Priority: Major
>             Fix For: 2.1.0
>
>
> Having a background service that triggers bottommost compaction for keyTable, fileTable, directoryTable, deletedTable, deletedDirectoryTable, multipartInfoTable (all the tables that can potentially be of a very large size) at a large interval like 6hours can help combat performance issues caused in the rocksDB layer. This can be turned off using a config. 
> This would be a fallback approach until HDDS-12518 design and implementation is completed.



--
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