Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1509358

Summary: [RHCS 3.y] Change default of rocksdb to no compression
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Mike Hackett <mhackett>
Component: RADOSAssignee: Josh Durgin <jdurgin>
Status: CLOSED ERRATA QA Contact: Parikshith <pbyregow>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: ceph-eng-bugs, ceph-qe-bugs, dzafman, gfarnum, hnallurv, kchai, kdreyer, tserlin, vumrao
Target Milestone: z2Keywords: FutureFeature
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.4-4.el7cp Ubuntu: ceph_12.2.4-5redhat1xenial Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-26 17:38:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1548067    
Bug Blocks:    

Description Mike Hackett 2017-11-03 15:37:32 UTC
Description of problem:
Disable compression by default on rocksdb.

Current Default:

filestore_rocksdb_options = "max_background_compactions=8;compaction_readahead_size=2097152"

Recommended change for default disabling compression:

filestore_rocksdb_options = "max_background_compactions=8;compaction_readahead_size=2097152;compression=kNoCompression"

Comment 3 Greg Farnum 2017-11-03 16:07:13 UTC
I do not believe disabling compression is an appropriate default. While it can help in some situations, compression reduces the amount of disk IO OSDs must perform.

Comment 6 Vikhyat Umrao 2017-11-10 14:25:23 UTC
Upstream Luminous backport - https://github.com/ceph/ceph/pull/18860

Comment 8 Ken Dreyer (Red Hat) 2018-03-26 15:24:47 UTC
PR 18860 landed in v12.2.2 upstream, so this bug will be resolved in the v12.2.4 rebase

Comment 19 errata-xmlrpc 2018-04-26 17:38:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:1259