Performance Related Configurations

This section documents how to configure Ozone to optimize performance.

📄️ Production Deployment

This document provides guidance on the requirements and best practices for a production deployment of Apache Ozone.

📄️ Topology

Apache Ozone uses topology information (e.g., rack placement) to optimize data access and improve resilience. A fully rack-aware cluster needs:

📄️ Multi-Raft

Multi-Raft in Datanodes

📄️ RocksDB In Apache Ozone

This page covers advanced topics. Ozone administration normally does not require changing these settings.

📄️ Streaming Write Pipeline

This document discusses the Streaming Write Pipeline feature in Ozone. It is implemented with the Ratis Streaming API.

📄️ Calculating EC Pipeline Limits

The target number of open EC pipelines SCM aims to maintain is calculated dynamically for each EC replication configuration (e.g., RS-6-3, RS-3-2). The calculation is based on the following two properties, with the final target being the greater of the two resulting values.

📄️ Calculating Ratis Pipeline Limits

ReplicationFactor.THREE is controlled by three configuration properties that limit the

📄️ S3 Gateway Load Balancing

The Ozone S3 Gateway is designed to be stateless, which means it does not store any data on the node where it is running. This stateless architecture allows you to run multiple S3 Gateway nodes and load balance traffic between them.

📄️ Fairness

What is FairCallQueue?

📄️ HttpFS load balancer (Kerberos)

Clients that use HTTP SPNEGO (negotiate authentication) obtain a Kerberos service ticket for the hostname they connect to. If HttpFS is reachable only through a load balancer, that hostname is the load balancer’s DNS name—not the individual HttpFS gateway hosts. Requests then fail with 401 Authentication required unless each HttpFS instance is configured to use the same HTTP service principal as the one clients expect for the load balancer.