Bug 1129609

Summary: Values for cache-priority should be validated
Product: [Community] GlusterFS Reporter: SATHEESARAN <sasundar>
Component: io-cacheAssignee: Raghavendra G <rgowdapp>
Status: CLOSED DEFERRED QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: bugs, smohan
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-22 14:18:36 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:

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: