- Features
- Decommissioning
- OM High Availability
- Ozone Erasure Coding
- Ozone Snapshot
- SCM High Availability
- Streaming Write Pipeline
- Merge Container RocksDB in DN
- Prefix based File System Optimization
- Topology awareness
- Quota in Ozone
- Recon Server
- Observability
- Non-Rolling Upgrades and Downgrades
- S3 Multi-Tenancy
- Reconfigurability
Features
Ozone Features
Ozone features are explained in the following pages. Features such as high availability, topology awareness, metrics tools are detailed in next pages.
Decommissioning
Decommissioning of SCM, OM and Datanode.
OM High Availability
HA setup for Ozone Manager to avoid any single point of failure.
Ozone Erasure Coding
Erasure Coding Support for Ozone.
Ozone Snapshot
Ozone Snapshot
SCM High Availability
HA setup for Storage Container Manager to avoid any single point of failure.
Streaming Write Pipeline
A new write pipeline using Ratis Streaming.
Merge Container RocksDB in DN
Introduction to Ozone Datanode Container Schema V3
Prefix based File System Optimization
Supports atomic rename and delete operation.
Topology awareness
Configuration for rack-awarness for improved read/write
Quota in Ozone
Introduction to Ozone Quota
Recon Server
Recon is the Web UI and analysis service for Ozone
Observability
Different tools for Ozone to increase Observability
Non-Rolling Upgrades and Downgrades
How to do non-rolling upgrades and downgrades of Ozone
S3 Multi-Tenancy
Ozone Multi-Tenancy that allows multiple tenants to share the same Ozone cluster. Compatible with S3 API.
Reconfigurability
Dynamic reloading configuration.
FairCallQueue This document contains information for setting up the FairCallQueue feature with Ozone. In order for FairCallQueue to be enabled and used, Hadoop RPC must be used as transport protocol for OM - S3G communication. There is no implementation for gRPC yet. There is a custom IdentityProvider implementation for Ozone that must be specified in the configuration, otherwise there is no S3G impersonation which makes the FairCallQueue ineffective since it’s only reading one user, the S3G special user instead of the S3G client user.