You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Krishna Kumar Asawa (Jira)" <ji...@apache.org> on 2025/02/07 13:20:00 UTC

[jira] [Assigned] (HDDS-12220) Add RocksDB maximum log file number to OM, SCM, and Recon

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

Krishna Kumar Asawa reassigned HDDS-12220:
------------------------------------------

    Assignee: Gargi Jaiswal

> Add RocksDB maximum log file number to OM, SCM, and Recon
> ---------------------------------------------------------
>
>                 Key: HDDS-12220
>                 URL: https://issues.apache.org/jira/browse/HDDS-12220
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: OM, Ozone Recon, SCM
>            Reporter: Ryan Blough
>            Assignee: Gargi Jaiswal
>            Priority: Minor
>              Labels: newbie
>
> It currently appears that the RocksDB LOG.old files can be generated without limit for OM, SCM, and Recon. I have observed these files filling up the disk, bringing down the Recon instance in a cluster.
> The DataNode has this property to control them: hdds.datanode.rocksdb.log.max-file-num
> Can we add a similar property for the other three? So:
> hdds.scm.rocksdb.log.max-file-num
> hdds.om.rocksdb.log.max-file-num
> hdds.recon.rocksdb.log.max-file-num
> One reasonable default value would be 10.



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