File System Optimization (FSO) System Internals | Apache Ozone
Skip to main content
Apache Ozone
Docs
Latest Docs
Docs 2.0.0 (Archived)
Docs 1.4.1 (Archived)DownloadRoadmapBlog
Community
Communication Channels
Who Uses Ozone?
Report An Issue
Ask a Question
How to Contribute
Events and Media
Search
Version:
2.2.0
Next
2.2.0
2.1.1
Overview
Quick Start
Core Concepts
User Guide
Administrator Guide
System Internals
Components
Data Operations
Data Integrity
Replication
Security
Network Protocols
Features
Filesystem Optimization (FSO)
Upgrade and Downgrade
Snapshot Deletion Lifecycle
Bucket Snapshot
Erasure Coding
Snapshot Defragmentation
OM Bootstrapping with Snapshots
Developer Guide
System Internals
Features
Filesystem Optimization (FSO)Version: 2.2.0
On this page
File System Optimization (FSO) System Internals
The prefix-based File System Optimization feature supports atomic rename and delete of any directory at any level in the
namespace in deterministic/constant time.
This feature can be enabled for each specific bucket that requires it by setting the --layout flag
to FILE_SYSTEM_OPTIMIZED at the time of bucket creation.
ozone sh bucket create /<volume-name>/<bucket-name> --layout FILE_SYSTEM_OPTIMIZED
Note: File System Optimization favors Hadoop Compatible File System instead of S3 compatibility. Some irregular S3 key
names may be rejected or normalized.
This feature is strongly recommended to be turned ON for Ozone buckets mainly used via Hadoop compatible interfaces,
especially with high number of files in deep directory hierarchy.
OzoneManager Metadata layout format​
OzoneManager supports two metadata bucket layout formats - Object Store (OBS) and File System Optimized (FSO).
Object Store (OBS) is the existing OM metadata format, which stores key entry with full path name. In File System
Optimized (FSO) buckets, OM metadata format stores intermediate directories into DirectoryTable and files
into FileTable as shown in the below picture. The key to the table is the name of a directory or a file prefixed by
the unique identifier of its parent directory, <parent unique-id>/<filename>.
Directory delete operation with prefix layout​
Following picture describes the OM metadata changes while performing a delete
operation on a directory.
Directory rename operation with prefix layout​
Following picture describes the OM metadata changes while performing a rename
operation on a directory.
Configuration​
The following configuration can be configured in ozone-site.xml to define the default value for bucket layout during bucket creation
if the client has not specified the bucket layout argument.
Supported values are OBJECT_STORE, FILE_SYSTEM_OPTIMIZED and LEGACY.
By default, this config value is empty. Ozone will default to FILE_SYSTEM_OPTIMIZED bucket layout if it finds an empty config value.
<property>
<name>ozone.default.bucket.layout</name>
<value/>
</property>
Edit this page
Previous
Features
Next
Upgrade and Downgrade
OzoneManager Metadata layout format
Directory delete operation with prefix layout
Directory rename operation with prefix layout
Configuration
Apache Software Foundation
Foundation
License
Events
Sponsorship
Privacy
Security
Thanks
Community
GitHub Discussions
Jira Issues
Slack
Mailing List
YouTube
Twitter
Repositories
Ozone
Website
Docker Image
Docker Runner Image
Copyright © 2026 The Apache Software Foundation. Licensed under the Apache License, Version 2.0.
The Apache Software Foundation, Apache Ozone, Ozone, Apache, the Apache Feather, and the Apache Ozone project logo are either registered trademarks or trademarks of the Apache Software Foundation.