Ozone

This documentation encompasses the setup of Ozone with ODP, orchestrated by Ambari as an mpack. Additionally, it provides details on Ozone configuration and functionalities, catering to various Hadoop-related services, S3, with or without security enabled, including authentication (Kerberos) and/or authorization (Ranger).

Ozone Storage Elements

Ozone, being an object storage for Hadoop, consists of volumes, buckets, and keys:

• Volume: Volumes are similar to user accounts. Only administrators can create or delete volumes. Ozone creates s3v volume during initialization to support S3 Protocol.
• Bucket: Buckets are similar to directories and reside in volume. It resembles Amazon S3 Buckets in terms of hierarchy and ACL. A bucket can contain any number of keys, but buckets cannot contain other buckets. OzoneManager supports two metadata bucket layout formats - Object Store (OBS) and File System Optimized (FSO). By default, Ozone sets all buckets layout to FILE_SYSTEM_OPTIMIZED but buckets under s3v volume are ofOBJECT_STORE layout.
• Key: Keys are similar to files.

For more information, refer the following documentations:

1. Ozone Configurations
2. Ozone Installation
3. Ozone Command Line Interface
4. Working with Ozone File System
5. Using Ozone S3 Gateway

Known Issues

• Ozone service check encounters failure when Ranger is enabled.
• The current configuration sets the Ozone Manager Java Heap size to half of the machine's RAM. Adjust the Java heap size as needed during installation.
• The Ozone mpack exclusively supports secure Ozone installations on freshly set up Ozone instances in Kerberized clusters.