Bug 1201628

Summary:	Tune dirty_ratio and dirty_background_ratio for RHS
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Ramesh N <rnachimu>
Component:	vdsm	Assignee:	Bala.FA <barumuga>
Status:	CLOSED ERRATA	QA Contact:	RamaKasturi <knarra>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	rhgs-3.0	CC:	annair, barumuga, dpati, knarra, nlevinki, rcyriac, rhs-bugs, sasundar, sharne
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.0.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	vdsm-4.16.8.1-6.2.el6rhs	Doc Type:	Bug Fix
Doc Text:	Virtual memory settings in Red Hat Storage is reset to Red Hat Enterprise Linux defaults to improve I/O performance.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-26 06:37:01 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:
Bug Blocks:	1182947

Description Ramesh N 2015-03-13 07:01:27 UTC

Description of problem:
 Currently dirty_ratio and dirty_background_ratio is changed to 5, 2 from RHEL's default 20, 10. But RHS performance teams suggest to keep it same as in RHEL for RHS.

 Tune the dirty_ratio and dirty_background_ratio accordingly to the values suggested by the RHS performance team:

vm.dirty_ratio=20
vm.dirty_background_ratio=10

Comment 2 Bala.FA 2015-03-13 08:54:06 UTC

The fix is done by removing settings in /etc/sysctl.d/vdsm.conf file.

Comment 4 Shalaka 2015-03-16 04:44:51 UTC

Please add doc text.

Comment 5 Shalaka 2015-03-16 07:53:23 UTC

Please review and sign-off edited doc text.

Comment 6 Bala.FA 2015-03-16 10:28:45 UTC

Looks good to me

Comment 8 errata-xmlrpc 2015-03-26 06:37:01 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://rhn.redhat.com/errata/RHBA-2015-0682.html