Bug 1129609 - Values for cache-priority should be validated
Summary: Values for cache-priority should be validated
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: io-cache
Version: mainline
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-13 10:52 UTC by SATHEESARAN
Modified: 2019-04-22 14:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-22 14:18:36 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description SATHEESARAN 2014-08-13 10:52:38 UTC
Description of problem:
-----------------------
cache-priority comes in to play while replacing the existing contents of the cache for giving way for the new entries. Its forms a base for retaining the files in cache based on the file types

We usually associate the ranking with the type of extensions
gluster volume set cache-priority <vol-name> "html:10,txt:5"

Currently the value for cache-priority is not validated.
It would be good to validate the values as user may accidentally provide wrong values.

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

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. gluster volume set cache-priority <vol-name> '\n'

Actual results:
---------------
value for cache-priority is not validated

Expected results:
-----------------
value for cache-priority could be validated

Additional info:


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