Technology

Apache Ozone

A scalable, distributed object storage system in the Hadoop ecosystem with an S3-compatible interface.

4 connections 3 resources

Summary

What it is

A scalable, distributed object storage system in the Hadoop ecosystem with an S3-compatible interface.

Where it fits

Ozone bridges the legacy Hadoop world (HDFS, YARN, MapReduce) and the modern S3-based world. It gives Hadoop-native workloads an S3 API while also supporting the Hadoop filesystem interface.

Misconceptions / Traps
  • Ozone is not a drop-in HDFS replacement. It has a different consistency model and metadata architecture (SCM + OM).
  • Adoption outside the Hadoop ecosystem is limited. If you don't have legacy Hadoop workloads, MinIO or AWS S3 are more practical choices.
Key Connections
  • implements S3 API — S3-compatible interface for Hadoop environments
  • solves Legacy Ingestion Bottlenecks — migration path from HDFS
  • scoped_to S3, Object Storage — part of the S3-compatible ecosystem

Definition

What it is

A scalable, distributed object storage system designed for the Hadoop ecosystem, with an S3-compatible interface.

Why it exists

Hadoop's HDFS does not scale well beyond a single namespace. Ozone provides a Hadoop-native object store that supports both the Hadoop filesystem interface and the S3 API, bridging legacy Hadoop workloads with modern S3-based architectures.

Primary use cases

S3-compatible storage for Hadoop-based data platforms, migration path from HDFS to object storage.

Recent developments

Latest signals
  • Apache Ozone 2.0.0 GA (August 2025) — 1,700 new features + fixes on top of 1.4. Major milestone release. The ASF positions 2.0 as the "evolution from Hadoop object store to modern cloud-native storage platform" — AI, lakehouse, and hybrid-cloud are the named target workloads. Per ASF News — Apache Ozone 2.0.0 announcement.
  • First object store to support Apache HBase natively. Enables low-latency read/write workloads alongside traditional object storage — Ozone collapses the "HBase needs HDFS / object store is too slow" tradeoff that historically split Hadoop clusters in two. Per Apache Ozone — 2.0.0 release notes.
  • S3 Gateway updated for AWS Java SDK v2 2.30.0 incompatibility. AWS SDK v2 introduced an upload-protocol change that silently appended trailer data or failed; Ozone's S3 Gateway is now updated to handle SDK v2 2.30.0 and later. Critical compatibility fix — older S3G versions silently corrupted uploads. Per Apache Ozone — 2.0.0 release notes.
  • AWS STS AssumeRole support added for short-lived credentials. Ozone S3G now generates temporary credentials via STS-style AssumeRole flow — eliminates long-lived access-key sprawl in multi-tenant Ozone clusters. Per Apache Ozone — 2.0.0 release notes.
  • S3 STANDARD_IA storage class + EC replication config support. Tiered-storage primitives now usable through the S3 API — clients can set storage class to infrequent-access at PUT time and reference erasure-coding replication configs. Closes a feature gap vs MinIO + Ceph RGW. Per Apache Ozone 2.0.0 release notes.
  • JDK 17 + 21 compatibility; native ARM64 builds. Ozone 2.0 builds and runs on modern Java + ARM64 — opens deployment to Graviton/Ampere clusters that the JDK-8/x86-only past locked out. Per Apache Ozone — 2.0.0 release notes and Globenewswire — ASF Announces Ozone 2.0.0.

Connections 4

Outbound 4

Resources 3