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
c4aa0e34
"tests/vscode:/vscode.git/clone" did not exist on "86555ae0f7cc45abac7f758d72bf456e90793b46"
Commit
c4aa0e34
authored
Dec 05, 2013
by
Ben
Committed by
antirez
Oct 06, 2014
Browse files
Grammar and typo fixes in redis.conf
Closes #1441
parent
cc4162ff
Changes
1
Hide whitespace changes
Inline
Side-by-side
redis.conf
View file @
c4aa0e34
...
...
@@ -15,7 +15,7 @@
################################## INCLUDES ###################################
# Include one or more other config files here. This is useful if you
# have a standard template that goes to all Redis server but also need
# have a standard template that goes to all Redis server
s
but also need
# to customize a few per-server settings. Include files can include
# other files, so use this wisely.
#
...
...
@@ -318,7 +318,7 @@ slave-priority 100
# The lag in seconds, that must be <= the specified value, is calculated from
# the last ping received from the slave, that is usually sent every second.
#
# This option does not GUARANTEE
S
that N replicas will accept the write, but
# This option does not GUARANTEE that N replicas will accept the write, but
# will limit the window of exposure for lost writes in case not enough slaves
# are available, to the specified number of seconds.
#
...
...
@@ -408,14 +408,14 @@ slave-priority 100
# is reached. You can select among five behaviors:
#
# volatile-lru -> remove the key with an expire set using an LRU algorithm
# allkeys-lru -> remove any key according
ly
to the LRU algorithm
# allkeys-lru -> remove any key according to the LRU algorithm
# volatile-random -> remove a random key with an expire set
# allkeys-random -> remove a random key, any key
# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
# noeviction -> don't expire at all, just return an error on write operations
#
# Note: with any of the above policies, Redis will return an error on write
# operations, when there are no
t
suitable keys for eviction.
# operations, when there are no suitable keys for eviction.
#
# At the date of writing this commands are: set setnx setex append
# incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
...
...
@@ -465,13 +465,13 @@ appendonly no
appendfilename
"appendonly.aof"
# The fsync() call tells the Operating System to actually write data on disk
# instead
t
o wait for more data in the output buffer. Some OS will really flush
# instead o
f
wait
ing
for more data in the output buffer. Some OS will really flush
# data on disk, some other OS will just try to do it ASAP.
#
# Redis supports three different modes:
#
# no: don't fsync, just let the OS flush the data when it wants. Faster.
# always: fsync after every write to the append only log
. Slow, Safest.
# always: fsync after every write to the append only log. Slow, Safest.
# everysec: fsync only one time every second. Compromise.
#
# The default is "everysec", as that's usually the right compromise between
...
...
@@ -564,11 +564,11 @@ aof-load-truncated yes
# still in execution after the maximum allowed time and will start to
# reply to queries with an error.
#
# When a long running script exceed the maximum execution time only the
# When a long running script exceed
s
the maximum execution time only the
# SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
# used to stop a script that did not yet called write commands. The second
# is the only way to shut down the server in the case a write command
s
was
# already issue by the script but the user don't want to wait for the natural
# is the only way to shut down the server in the case a write command was
# already issue
d
by the script but the user do
es
n't want to wait for the natural
# termination of the script.
#
# Set it to 0 or a negative value for unlimited execution without warnings.
...
...
@@ -585,7 +585,7 @@ lua-time-limit 5000
# Every cluster node has a cluster configuration file. This file is not
# intended to be edited by hand. It is created and updated by Redis nodes.
# Every Redis Cluster node requires a different cluster configuration file.
# Make sure that instances running in the same system do
es
not have
# Make sure that instances running in the same system do not have
# overlapping cluster configuration file names.
#
# cluster-config-file nodes-6379.conf
...
...
@@ -749,8 +749,8 @@ latency-monitor-threshold 0
# A Alias for g$lshzxe, so that the "AKE" string means all the events.
#
# The "notify-keyspace-events" takes as argument a string that is composed
#
by
zero or multiple characters. The empty string means that notifications
# are disabled
at all
.
#
of
zero or multiple characters. The empty string means that notifications
# are disabled.
#
# Example: to enable list and generic events, from the point of view of the
# event name, use:
...
...
@@ -782,7 +782,7 @@ list-max-ziplist-entries 512
list
-
max
-
ziplist
-
value
64
# Sets have a special encoding in just one case: when a set is composed
# of just strings that happen
s
to be integers in radix 10 in the range
# of just strings that happen to be integers in radix 10 in the range
# of 64 bit signed integers.
# The following configuration setting sets the limit in the size of the
# set in order to use this special memory saving encoding.
...
...
@@ -817,11 +817,11 @@ hll-sparse-max-bytes 3000
# by the hash table.
#
# The default is to use this millisecond 10 times every second in order to
# active rehash
ing
the main dictionaries, freeing memory when possible.
# active
ly
rehash the main dictionaries, freeing memory when possible.
#
# If unsure:
# use "activerehashing no" if you have hard latency requirements and it is
# not a good thing in your environment that Redis can reply f
o
rm time to time
# not a good thing in your environment that Redis can reply fr
o
m time to time
# to queries with 2 milliseconds delay.
#
# use "activerehashing yes" if you don't have such hard requirements but
...
...
@@ -870,7 +870,7 @@ client-output-buffer-limit pubsub 32mb 8mb 60
# never requested, and so forth.
#
# Not all tasks are performed with the same frequency, but Redis checks for
# tasks to perform according
ly
to the specified "hz" value.
# tasks to perform according to the specified "hz" value.
#
# By default "hz" is set to 10. Raising the value will use more CPU when
# Redis is idle, but at the same time will make Redis more responsive when
...
...
@@ -887,4 +887,3 @@ hz 10
# in order to commit the file to the disk more incrementally and avoid
# big latency spikes.
aof
-
rewrite
-
incremental
-
fsync
yes
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