Ozone2 Known Issues / Limitations

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

• HA and non-HA Ozone installations are supported only for fresh installations. Non-HA to HA migration is not yet certified.