andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

nl-cache: Remove the max limit for nl-cache-limit and nl-cache-timeout

Browse Source 
The max limit is better unset when arbitrary. Otherwise in the future
if max has to be changed, it can break backward compatility.

Change-Id: I4337a3789a2d0d5cc8e2bf687a22536c97608461
BUG: 1442569
Signed-off-by: Poornima G <pgurusid@redhat.com>
Reviewed-on: https://review.gluster.org/17261
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
This commit is contained in:
Poornima G 2017-05-12 10:27:28 +05:30 committed by Jeff Darcy
parent ba0fc77947
commit 64f41b962b
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
xlators/performance/nl-cache/src/nl-cache.c
View File

@ -762,7 +762,6 @@ struct volume_options options[] = {
{ .key = {"nl-cache-limit"},
.type = GF_OPTION_TYPE_SIZET,
.min = 0,
.max = 100 * GF_UNIT_MB,
.default_value = "131072",
.description = "the value over which caching will be disabled for"
"a while and the cache is cleared based on LRU",
@ -770,7 +769,6 @@ struct volume_options options[] = {
{ .key = {"nl-cache-timeout"},
.type = GF_OPTION_TYPE_TIME,
.min = 0,
.max = 1 * GF_DAY_IN_SECONDS,
.default_value = "60",
.description = "Time period after which cache has to be refreshed",
},