Bug 1387563

Summary:	[RFE]: md-cache performance enhancement
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	rjoseph
Component:	md-cache	Assignee:	Michael Adam <madam>
Status:	CLOSED ERRATA	QA Contact:	surabhi <sbhaloth>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.2	CC:	amukherj, asrivast, rcyriac, rhs-bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	RHGS 3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8.4-3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-23 06:14:31 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:	1284873
Bug Blocks:	1351503

Description rjoseph 2016-10-21 09:21:16 UTC

Description of problem:

Currently md-cache invalidation timeout is 1 min which is very low. For improving performance we need to increase this timeout. But increasing the timeout can lead to stale cache issues. Therefore provide a way for cache invalidation.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Atin Mukherjee 2016-10-22 13:50:27 UTC

Please refer to BZ 1284873 for the list of patches.

Comment 5 surabhi 2016-12-15 11:17:43 UTC

The 3.2 builds are received with md-cache changes and is qualified with core components.The documentation is in plac ein under review. the default value for cache invalidation is 1 min , and as per recommendation and doc , QE has tested it with 600 secs.

Since the functionality is present in current build od 3.2 closing this RFE. Any further bugs uncovered in testing will open a new Bugzilla for md-cache.

marking it Verified.glusterfs-3.8.4-8.el7rhgs.x86_64

Comment 7 errata-xmlrpc 2017-03-23 06:14:31 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/RHSA-2017-0486.html