Skip to content

Conversation

@Gargi-jais11
Copy link

@Gargi-jais11 Gargi-jais11 commented Jan 12, 2026

What changes were proposed in this pull request?

Migrate the v1 doc "RocksDB in Apache Ozone" https://ozone.apache.org/docs/edge/concept/rocksdb.html to v2 doc: under Administrator Guide -> Configuration -> Performance

https://ozone-site-v2.staged.apache.org/docs/administrator-guide/configuration/performance/

What is the link to the Apache Jira?

https://issues.apache.org/jira/browse/HDDS-14395

How was this patch tested?

Check off which of the following tests were done on this change. If additional testing was done, please elaborate here as well.

  • The CI checks on my fork are passing
  • I verified the rendered content using a local preview
  • I manually verified the steps provided in this change work as described

@Gargi-jais11
Copy link
Author

Gargi-jais11 commented Jan 12, 2026

@jojochuang I found out that there are some more configurations related to RocksDB in the codebase.
How about adding these as well in the doc for v2 doc under Tunings applicable to RocksDB?
General Settings:

  • ozone.metastore.rocksdb.statistics: The statistics level of the RocksDB store. If set to any value from org.rocksdb.StatsLevel (e.g., ALL or EXCEPT_DETAILED_TIMERS), RocksDB statistics will be exposed over JMX. Set to OFF to disable statistics collection. Note: collecting statistics can have a 5–10% performance penalty. Default: OFF.

Ozone Manager (OM) Specific Settings

  • ozone.om.snapshot.rocksdb.metrics.enabled: Enable or disable detailed RocksDB metrics for snapshot databases. Default: false.
  • ozone.om.snapshot.db.max.open.files: Maximum number of open files for each snapshot RocksDB instance. Default: 100.
  • ozone.om.snapshot.cache.max.size: Maximum size of the snapshot cache (soft limit), controlling how many snapshot RocksDB instances are kept open. Default: 10.

DataNode-Specific Settings:

  • hdds.datanode.db.config.path: Path to an INI configuration file for advanced RocksDB tuning on datanodes. Default: empty (not configured).
  • hdds.datanode.container.schema.v3.enabled: Enable container schema v3 (one RocksDB per disk). Default: true.
  • hdds.datanode.container.schema.v3.key.separator: The separator between Container ID and container meta key name in schema v3. Default: "|".

@jojochuang
Copy link
Contributor

Thanks for double check. Yeah those look good.

The OM snapshot related configuration properties are mention in the Ozone Snapshot section. No need to duplicate here.
The https://ozone-site-v2.staged.apache.org/docs/administrator-guide/operations/snapshots/configuration-properties

@Gargi-jais11
Copy link
Author

Thanks for double check. Yeah those look good.

The OM snapshot related configuration properties are mention in the Ozone Snapshot section. No need to duplicate here. The https://ozone-site-v2.staged.apache.org/docs/administrator-guide/operations/snapshots/configuration-properties

So I can add these expect OM ones:
General Settings:

ozone.metastore.rocksdb.statistics: The statistics level of the RocksDB store. If set to any value from org.rocksdb.StatsLevel (e.g., ALL or EXCEPT_DETAILED_TIMERS), RocksDB statistics will be exposed over JMX. Set to OFF to disable statistics collection. Note: collecting statistics can have a 5–10% performance penalty. Default: OFF.

DataNode-Specific Settings:

hdds.datanode.db.config.path: Path to an INI configuration file for advanced RocksDB tuning on datanodes. Default: empty (not configured).
hdds.datanode.container.schema.v3.enabled: Enable container schema v3 (one RocksDB per disk). Default: true.
hdds.datanode.container.schema.v3.key.separator: The separator between Container ID and container meta key name in schema v3. Default: "|".

@jojochuang
Copy link
Contributor

Yes those are good

@Gargi-jais11
Copy link
Author

Yes those are good

done

@jojochuang jojochuang merged commit 6f704ae into apache:HDDS-9225-website-v2 Jan 14, 2026
11 checks passed
@jojochuang
Copy link
Contributor

Merged. Thanks @Gargi-jais11 !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants