Bug 1929680 - [Doc RFE] Document support for better space utilization for small objects
Summary: [Doc RFE] Document support for better space utilization for small objects
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 5.0
Assignee: Ranjini M N
QA Contact: skanta
URL:
Whiteboard:
: 1952800 (view as bug list)
Depends On: 1952800
Blocks: 1929147
TreeView+ depends on / blocked
 
Reported: 2021-02-17 12:27 UTC by Anjana Suparna Sriram
Modified: 2021-09-09 12:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
.Small objects and files in RADOS no longer use more space than required The Ceph Object Gateway and the Ceph file system (CephFS) stores small objects and files as individual objects in RADOS. Previously, objects smaller than BlueStore's default minimum allocation size (`min_alloc_size`) used more space than required. This happened because the earlier default value of BlueStore's `min_alloc_size` was 16 KB for solid state devices (SSDs) and 64 KB for (HDDs). Currently, the default value of `min_alloc_size` for SSDs and HDDs is 4 KB. This enables better use of space with no impact on performance.
Clone Of:
Environment:
Last Closed: 2021-09-09 11:57:11 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-1519 0 None None None 2021-09-09 12:01:50 UTC

Comment 9 skanta 2021-04-23 08:37:32 UTC
In the provided doc noticed that the configurations are setting using ansible-playbook and this is not supported in ceph 5.0. Created a bug for the same.
Hence assigning the bug again.

Comment 15 skanta 2021-04-30 04:47:29 UTC
Verified the Document mentioned at - https://bugzilla.redhat.com/show_bug.cgi?id=1929680#c13.

Comment 16 Ranjini M N 2021-06-17 13:40:07 UTC
*** Bug 1952800 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.