Bug 1898781

Summary:	trash: Create inode_table only while feature is enabled
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Mohit Agrawal <moagrawa>
Component:	core	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED ERRATA	QA Contact:	Sayalee <saraut>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.5	CC:	lgangava, pprakash, puebele, rhs-bugs, sajmoham, sheggodu, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.5.z Batch Update 4
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-6.0-50	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-29 07:21:03 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:

Description Mohit Agrawal 2020-11-18 04:05:40 UTC

Currently trash xlator creates a inode table(1M) even if feature is not enabled.
In brick_mux environment while 250 bricks are attached with a single brick process and feature is not enable brick process consumes 250M system memory unnecessarily per brick process.

Comment 1 Mohit Agrawal 2020-11-18 04:07:29 UTC

The upstream committed patch link
https://github.com/gluster/glusterfs/issues/1543

Comment 19 errata-xmlrpc 2021-04-29 07:21:03 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 (glusterfs bug fix and enhancement update), 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-2021:1462