Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ruanhaishen
redis
Commits
fd8f39a2
Commit
fd8f39a2
authored
Apr 29, 2020
by
antirez
Browse files
Fix tracking table max keys option in redis.conf.
parent
551fed31
Changes
1
Hide whitespace changes
Inline
Side-by-side
redis.conf
View file @
fd8f39a2
...
...
@@ -626,20 +626,23 @@ replica-priority 100
# to track the keys fetched by many clients.
#
# For this reason it is possible to configure a maximum fill value for the
# invalidation table. By default it is set to 1
0%
, and once this limit
is
# reached, Redis will start to evict
caching slot
s in the invalidation table
# even if
keys a
re not modified, just to reclaim memory: this will in turn
# invalidation table. By default it is set to 1
M of keys
, and once this limit
#
is
reached, Redis will start to evict
key
s in the invalidation table
# even if
they we
re not modified, just to reclaim memory: this will in turn
# force the clients to invalidate the cached values. Basically the table
# maximum
fill rat
e is a trade off between the memory you want to spend server
# maximum
siz
e is a trade off between the memory you want to spend server
# side to track information about who cached what, and the ability of clients
# to retain cached objects in memory.
#
# If you set the value to 0, it means there are no limits, and
all the 16
#
millions of caching slot
s
c
an
be us
ed
at
the
same time. In the "stats"
# INFO section, you can find information about the
amount of caching slots
#
used
at every given moment.
# If you set the value to 0, it means there are no limits, and
Redis will
#
retain a
s
m
an
y keys as need
ed
in
the
invalidation table.
#
In the "stats"
INFO section, you can find information about the
number of
#
keys in the invalidation table
at every given moment.
#
# tracking-table-max-fill 10
# Note: when key tracking is used in broadcasting mode, no memory is used
# in the server side so this setting is useless.
#
# tracking-table-max-keys 1000000
################################## SECURITY ###################################
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment