Bug 1524323 - No need to load ctr xlator if user has not configured tiering
Summary: No need to load ctr xlator if user has not configured tiering
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: hari gowtham
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-11 09:23 UTC by Mohit Agrawal
Modified: 2018-10-23 15:06 UTC (History)
3 users (show)

Fixed In Version: glusterfs-5.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-23 15:06:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Mohit Agrawal 2017-12-11 09:23:26 UTC
Description of problem:
Currently, we do still load ctr xlator even user has not configured tier.Due to this it unnecessarily consumes resources even it not required. 

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


How reproducible:


Steps to Reproduce:
1.Setup any volume and check the brick messages
2.It shows messages CTR Xlator is disabled
3.check volume file ctr xlator is still loaded.

Actual results:
ctr xlator is loaded even tier is not configured

Expected results:
ctr xlator should not be load if tier is not configured

Additional info:

Comment 1 Worker Ant 2017-12-11 10:30:02 UTC
REVIEW: https://review.gluster.org/19020 (CTR/glusterd: do not load CTR by default) posted (#1) for review on master by hari gowtham

Comment 2 hari gowtham 2017-12-11 11:46:33 UTC
The issue was come across by Mohit while working on https://bugzilla.redhat.com/show_bug.cgi?id=1524336

Comment 3 hari gowtham 2018-08-13 10:25:23 UTC
The above patch was abandoned.

A new patch for this issue is at: https://review.gluster.org/20501/

Comment 4 Worker Ant 2018-08-13 12:01:39 UTC
REVIEW: https://review.gluster.org/20501 (glusterd: do not load ctr xlator by default) posted (#5) for review on master by hari gowtham

Comment 5 Worker Ant 2018-08-24 05:19:04 UTC
REVIEW: https://review.gluster.org/20984 (ctr: skip ctr xlator init if ctr is not enabled) posted (#1) for review on master by MOHIT AGRAWAL

Comment 6 Worker Ant 2018-08-27 03:25:20 UTC
COMMIT: https://review.gluster.org/20984 committed in master by "Amar Tumballi" <amarts> with a commit message- ctr: skip ctr xlator init if ctr is not enabled

Problem: If ctr xlator is not required it consumes
         resources unnecessarily

Solution: Call ctr xlator init only while feature is enabled

Fixes: bz#1524323

Change-Id: I378113a390a286be20c4ade1b1bac170a8ef1b14
Signed-off-by: Mohit Agrawal <moagrawal>

Comment 7 Shyamsundar 2018-10-23 15:06:35 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/


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