Search
Documentation
ODP 3.3.6.4-1
Release Notes
What is ODP
Installation
Component User guide and Installation Instructions
Upgrade Instructions
Downgrade Instructions
Reference Guide
Security Guide
Troubleshooting Guide
Uninstall ODP
Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Ozone2 Known Issues / Limitations
Summarize Page
Copy Markdown
Open in ChatGPT
Open in Claude
Connect to Cursor
Connect to VS Code
This page lists the known limitations related to Ozone2.
Only a single Ozone installation is supported per cluster.
Currently, the Ozone Manager Java heap size is configured to use half of the machine RAM. Adjust the Java heap size as required during installation.
The Ozone mpack supports secure Ozone only on fresh Ozone installations on Kerberized clusters.
In the new Ozone2 mpack, the S3 Gateway (S3G) web utility has been split across two separate ports, which may result in warning alerts being displayed. Reference: https://issues.apache.org/jira/browse/HDDS-7307 Default ports:
- JMX operations port:
19878 - S3 Gateway static content endpoint:
9878
- JMX operations port:
HA and non-HA Ozone installations are supported only for fresh installations. Non-HA to HA migration is not yet certified.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Last updated on May 19, 2026
Was this page helpful?
Next to read:
Pinotnull
Discard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message