Bug 798546 - [glusterfs-3.3.0qa24]: create set command for md-cache & remove stat-prefetch set
Summary: [glusterfs-3.3.0qa24]: create set command for md-cache & remove stat-prefetch...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.7.5
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-29 08:48 UTC by Rahul C S
Modified: 2016-01-13 06:23 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-01-13 06:23:43 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Rahul C S 2012-02-29 08:48:27 UTC
Description of problem:
There is no md-cache set option, I know stat-prefetch set does the same thing, but since stat-prefetch is not present now, we need to make a md-cache set/unset command.

gluster volume set md-cache on/off

Comment 2 Amar Tumballi 2012-12-21 05:48:14 UTC
still a valid bug, but we need to keep backward compatibility, hence need to keep stat-prefetch, and add md-cache. Need to see how to achieve this.

Comment 3 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.

Comment 4 Sachidananda Urs 2015-12-14 10:27:54 UTC
This is still a bug. Since we always refer the feature as md-cache and not stat-prefetch ...

gluster vol set volname md-cache on/off 

Is the intuitive command.

Comment 5 Atin Mukherjee 2016-01-13 04:36:00 UTC
This has been already fixed and md-cache option is available now.

Comment 6 Atin Mukherjee 2016-01-13 06:19:52 UTC
I misread the code. md-cache option is still not introduced. Reopening the bug. Also assigning it to Raghavendra G as he is the maintainer of performance translators.

Comment 7 Atin Mukherjee 2016-01-13 06:23:43 UTC
With the current infrastructure of managing op-versions, this would be difficult to fix considering the backward compatibility. Until and unless we have some design changes of managing the VME table this is not a easy fix. I'd consider not to fix this issue at this stage since GlusterD 2.0 is going to ease out in maintaining the op-versions & backward compatibility.


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