Creating indexless buckets
You can configure a placement target where created buckets do not use the bucket index to store objects index; that is, indexless buckets. Placement targets that do not use data replication or listing might implement indexless buckets. Indexless buckets provide a mechanism in which the placement target does not track objects in specific buckets. Indexless buckets removes a resource contention that happens whenever an object write happens and reduces the number of round-trips that Ceph Object Gateway needs to make to the Ceph storage cluster. This can have a positive effect on concurrent operations and small object write performance.
Before you begin
- A running IBM Storage Ceph cluster.
- Installation of the Ceph Object Gateway software.
- Root-level access to a Ceph Object Gateway node.
About this task
Important: The bucket index does not reflect the correct state of the bucket, and
listing these buckets does not correctly return their list of objects, which affects multiple
features. Specifically, these buckets are not synced in a multi-zone environment because the bucket
index is not used to store change information. Do not to use S3 object versioning on indexless
buckets because the bucket index is necessary for this feature.
Note: Using indexless buckets removes the limit of the max number of objects in a single
bucket.