1. Units單位
   

   # Note that in order to read the configuration file, Redis must be
   # started with the file path as first argument:
   #
   # ./redis-server /path/to/redis.conf# Note on units: when memory size is needed, it is possible to specify
   # it in the usual form of 1k 5GB 4M and so forth:
   #
   # 1k => 1000 bytes
   # 1kb => 1024 bytes
   # 1m => 1000000 bytes
   # 1mb => 1024*1024 bytes
   # 1g => 1000000000 bytes
   # 1gb => 1024*1024*1024 bytes
   #
   # units are case insensitive so 1GB 1Gb 1gB are all the same.

   
   ① 配置大小單位，開頭定義了一些基本的度量單位，只支持bytes,不支持bit
   ② 對(duì)大小寫不敏感
   
   
2. INCLUDES包含
   

   ################################## INCLUDES #################################### Include one or more other config files here.  This is useful if you
   # have a standard template that goes to all Redis servers but also need
   # to customize a few per-server settings.  Include files can include
   # other files, so use this wisely.
   #
   # Notice option "include" won't be rewritten by command "CONFIG REWRITE"
   # from admin or Redis Sentinel. Since Redis always uses the last processed
   # line as value of a configuration directive, you'd better put includes
   # at the beginning of this file to avoid overwriting config change at runtime.
   #
   # If instead you are interested in using includes to override configuration
   # options, it is better to use include as the last line.
   #
   # include /path/to/local.conf
   # include /path/to/other.conf
   

   ① 和Struts2配置文件類似，可以通過includes包含其他的配置文件，redis.conf可以作為總閘，包含其他
   
   
   
   
3. ?NETWORK
   

   ################################## NETWORK ###################################### By default, if no "bind" configuration directive is specified, Redis listens
   # for connections from all the network interfaces available on the server.
   # It is possible to listen to just one or multiple selected interfaces using
   # the "bind" configuration directive, followed by one or more IP addresses.
   #
   # Examples:
   #
   # bind 192.168.1.100 10.0.0.1
   # bind 127.0.0.1 ::1
   #
   # ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the
   # internet, binding to all the interfaces is dangerous and will expose the
   # instance to everybody on the internet. So by default we uncomment the
   # following bind directive, that will force Redis to listen only into
   # the IPv4 lookback interface address (this means Redis will be able to
   # accept connections only from clients running into the same computer it
   # is running).
   #
   # IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES
   # JUST COMMENT THE FOLLOWING LINE.
   # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   bind 127.0.0.1# Protected mode is a layer of security protection, in order to avoid that
   # Redis instances left open on the internet are accessed and exploited.
   #
   # When protected mode is on and if:
   #
   # 1) The server is not binding explicitly to a set of addresses using the
   #    "bind" directive.
   # 2) No password is configured.
   #
   # The server only accepts connections from clients connecting from the
   # IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain
   # sockets.
   #
   # By default protected mode is enabled. You should disable it only if
   # you are sure you want clients from other hosts to connect to Redis
   # even if no authentication is configured, nor a specific set of interfaces
   # are explicitly listed using the "bind" directive.
   protected-mode yes# Accept connections on the specified port, default is 6379 (IANA #815344).
   # If port 0 is specified Redis will not listen on a TCP socket.
   port 6379# TCP listen() backlog.
   #
   # In high requests-per-second environments you need an high backlog in order
   # to avoid slow clients connections issues. Note that the Linux kernel
   # will silently truncate it to the value of /proc/sys/net/core/somaxconn so
   # make sure to raise both the value of somaxconn and tcp_max_syn_backlog
   # in order to get the desired effect.
   tcp-backlog 511# Unix socket.
   #
   # Specify the path for the Unix socket that will be used to listen for
   # incoming connections. There is no default, so Redis will not listen
   # on a unix socket when not specified.
   #
   # unixsocket /tmp/redis.sock
   # unixsocketperm 700# Close the connection after a client is idle for N seconds (0 to disable)
   timeout 0# TCP keepalive.
   #
   # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
   # of communication. This is useful for two reasons:
   #
   # 1) Detect dead peers.
   # 2) Take the connection alive from the point of view of network
   #    equipment in the middle.
   #
   # On Linux, the specified value (in seconds) is the period used to send ACKs.
   # Note that to close the connection the double of the time is needed.
   # On other kernels the period depends on the kernel configuration.
   #
   # A reasonable value for this option is 300 seconds, which is the new
   # Redis default starting with Redis 3.2.1.
   tcp-keepalive 300
   

   ① bind ip地址的綁定，默認(rèn)只允許本機(jī)訪問（127.0.0.1）。
   ②port ? 端口號(hào)?
   ③tcp-backlog ? ? 設(shè)置tcp的backlog,backlog其實(shí)是一個(gè)連接隊(duì)列，backlog隊(duì)列總和=未完成三次握手隊(duì)列+已經(jīng)完成三次握手隊(duì)列。在高并發(fā)開發(fā)環(huán)境下你需要一個(gè)高backlog值來避免慢客戶端連接的問題。注意Linux內(nèi)核會(huì)將這個(gè)值減少到/proc/sys/net/core/somaxconn的值，所以需要確認(rèn)增大somaxconn和tcp_max_syn_backlog兩個(gè)值來達(dá)到想要的效果。
   ④ timeout 會(huì)話超時(shí)時(shí)間，默認(rèn)為0 ，不超時(shí)（不關(guān)閉會(huì)話）
   ⑤ tcp-keepalive 單位為秒，如果設(shè)置為0，則不會(huì)進(jìn)行keepalive檢測(cè)，建議設(shè)置為60（檢測(cè)redis的網(wǎng)絡(luò)通訊狀態(tài)）
   
   
4. GENERAL通用【通用配置】
   

   ################################# GENERAL ###################################### By default Redis does not run as a daemon. Use 'yes' if you need it.
   # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
   daemonize no# If you run Redis from upstart or systemd, Redis can interact with your
   # supervision tree. Options:
   #   supervised no      - no supervision interaction
   #   supervised upstart - signal upstart by putting Redis into SIGSTOP mode
   #   supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET
   #   supervised auto    - detect upstart or systemd method based on
   #                        UPSTART_JOB or NOTIFY_SOCKET environment variables
   # Note: these supervision methods only signal "process is ready."
   #       They do not enable continuous liveness pings back to your supervisor.
   supervised no# If a pid file is specified, Redis writes it where specified at startup
   # and removes it at exit.
   #
   # When the server runs non daemonized, no pid file is created if none is
   # specified in the configuration. When the server is daemonized, the pid file
   # is used even if not specified, defaulting to "/var/run/redis.pid".
   #
   # Creating a pid file is best effort: if Redis is not able to create it
   # nothing bad happens, the server will start and run normally.
   pidfile /var/run/redis_6379.pid# Specify the server verbosity level.
   # This can be one of:
   # debug (a lot of information, useful for development/testing)
   # verbose (many rarely useful info, but not a mess like the debug level)
   # notice (moderately verbose, what you want in production probably)
   # warning (only very important / critical messages are logged)
   loglevel notice# Specify the log file name. Also the empty string can be used to force
   # Redis to log on the standard output. Note that if you use standard
   # output for logging but daemonize, logs will be sent to /dev/null
   logfile ""# To enable logging to the system logger, just set 'syslog-enabled' to yes,
   # and optionally update the other syslog parameters to suit your needs.
   # syslog-enabled no# Specify the syslog identity.
   # syslog-ident redis# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
   # syslog-facility local0# Set the number of databases. The default database is DB 0, you can select
   # a different one on a per-connection basis using SELECT <dbid> where
   # dbid is a number between 0 and 'databases'-1
   databases 16

   
   ① daemonize ? 決定redis是否后臺(tái)運(yùn)行的配置，默認(rèn) no （不開啟），yes（開啟）
   ② pidfile Redis進(jìn)程PID文件所在路徑
   ③ loglevel 日志級(jí)別，有四個(gè)級(jí)別（debug/verbose/notice/wrning）
   ④?syslog-enabled 是否把日志輸出到syslog（系統(tǒng)日志）中
   ⑤ syslog-ident 指定syslog里的日志標(biāo)志
   ⑥ syslog-facility 指定syslog設(shè)備，值可以是USER或LOCAL0-LOCAL7
   ⑦ databases redis默認(rèn)分16個(gè)庫
   
   
5. SNAPSHOTTING 快照
   

   ################################ SNAPSHOTTING  ################################
   #
   # Save the DB on disk:
   #
   #   save <seconds> <changes>
   #
   #   Will save the DB if both the given number of seconds and the given
   #   number of write operations against the DB occurred.
   #
   #   In the example below the behaviour will be to save:
   #   after 900 sec (15 min) if at least 1 key changed
   #   after 300 sec (5 min) if at least 10 keys changed
   #   after 60 sec if at least 10000 keys changed
   #
   #   Note: you can disable saving completely by commenting out all "save" lines.
   #
   #   It is also possible to remove all the previously configured save
   #   points by adding a save directive with a single empty string argument
   #   like in the following example:
   #
   #   save ""save 900 1
   save 300 10
   save 60 10000# By default Redis will stop accepting writes if RDB snapshots are enabled
   # (at least one save point) and the latest background save failed.
   # This will make the user aware (in a hard way) that data is not persisting
   # on disk properly, otherwise chances are that no one will notice and some
   # disaster will happen.
   #
   # If the background saving process will start working again Redis will
   # automatically allow writes again.
   #
   # However if you have setup your proper monitoring of the Redis server
   # and persistence, you may want to disable this feature so that Redis will
   # continue to work as usual even if there are problems with disk,
   # permissions, and so forth.
   stop-writes-on-bgsave-error yes# Compress string objects using LZF when dump .rdb databases?
   # For default that's set to 'yes' as it's almost always a win.
   # If you want to save some CPU in the saving child set it to 'no' but
   # the dataset will likely be bigger if you have compressible values or keys.
   rdbcompression yes# Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
   # This makes the format more resistant to corruption but there is a performance
   # hit to pay (around 10%) when saving and loading RDB files, so you can disable it
   # for maximum performances.
   #
   # RDB files created with checksum disabled have a checksum of zero that will
   # tell the loading code to skip the check.
   rdbchecksum yes# The filename where to dump the DB
   dbfilename dump.rdb# The working directory.
   #
   # The DB will be written inside this directory, with the filename specified
   # above using the 'dbfilename' configuration directive.
   #
   # The Append Only File will also be created inside this directory.
   #
   # Note that you must specify a directory here, not a file name.
   dir ./

   
   
   
6. ?SECURITY安全【通用配置】
   

   ################################## SECURITY #################################### Require clients to issue AUTH <PASSWORD> before processing any other
   # commands.  This might be useful in environments in which you do not trust
   # others with access to the host running redis-server.
   #
   # This should stay commented out for backward compatibility and because most
   # people do not need auth (e.g. they run their own servers).
   #
   # Warning: since Redis is pretty fast an outside user can try up to
   # 150k passwords per second against a good box. This means that you should
   # use a very strong password otherwise it will be very easy to break.
   #
   # requirepass foobared# Command renaming.
   #
   # It is possible to change the name of dangerous commands in a shared
   # environment. For instance the CONFIG command may be renamed into something
   # hard to guess so that it will still be available for internal-use tools
   # but not available for general clients.
   #
   # Example:
   #
   # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
   #
   # It is also possible to completely kill a command by renaming it into
   # an empty string:
   #
   # rename-command CONFIG ""
   #
   # Please note that changing the name of commands that are logged into the
   # AOF file or transmitted to slaves may cause problems.
   

   ① requirepass 密碼，redis默認(rèn)是不開啟安全驗(yàn)證的，其目的是更關(guān)注與緩存這塊而非安全
   備注：如果一旦設(shè)置了密碼，意味著操作redis之前都必須通過?AUTH命令（auth ?password） 進(jìn)行授權(quán)驗(yàn)證。
   
   
7. ?LIMITS限制【通用配置】
   

   ################################### LIMITS ##################################### Set the max number of connected clients at the same time. By default
   # this limit is set to 10000 clients, however if the Redis server is not
   # able to configure the process file limit to allow for the specified limit
   # the max number of allowed clients is set to the current file limit
   # minus 32 (as Redis reserves a few file descriptors for internal uses).
   #
   # Once the limit is reached Redis will close all the new connections sending
   # an error 'max number of clients reached'.
   #
   # maxclients 10000# Don't use more memory than the specified amount of bytes.
   # When the memory limit is reached Redis will try to remove keys
   # according to the eviction policy selected (see maxmemory-policy).
   #
   # If Redis can't remove keys according to the policy, or if the policy is
   # set to 'noeviction', Redis will start to reply with errors to commands
   # that would use more memory, like SET, LPUSH, and so on, and will continue
   # to reply to read-only commands like GET.
   #
   # This option is usually useful when using Redis as an LRU cache, or to set
   # a hard memory limit for an instance (using the 'noeviction' policy).
   #
   # WARNING: If you have slaves attached to an instance with maxmemory on,
   # the size of the output buffers needed to feed the slaves are subtracted
   # from the used memory count, so that network problems / resyncs will
   # not trigger a loop where keys are evicted, and in turn the output
   # buffer of slaves is full with DELs of keys evicted triggering the deletion
   # of more keys, and so forth until the database is completely emptied.
   #
   # In short... if you have slaves attached it is suggested that you set a lower
   # limit for maxmemory so that there is some free RAM on the system for slave
   # output buffers (but this is not needed if the policy is 'noeviction').
   #
   # maxmemory <bytes># MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
   # 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 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 suitable keys for eviction.
   #
   #       At the date of writing these commands are: set setnx setex append
   #       incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
   #       sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
   #       zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
   #       getset mset msetnx exec sort
   #
   # The default is:
   #
   # maxmemory-policy noeviction# LRU and minimal TTL algorithms are not precise algorithms but approximated
   # algorithms (in order to save memory), so you can tune it for speed or
   # accuracy. For default Redis will check five keys and pick the one that was
   # used less recently, you can change the sample size using the following
   # configuration directive.
   #
   # The default of 5 produces good enough results. 10 Approximates very closely
   # true LRU but costs a bit more CPU. 3 is very fast but not very accurate.
   #
   # maxmemory-samples 5
   

   ①?maxclients 最大客戶端連接數(shù)
   ②?maxmemory 最大內(nèi)存，單位<bytes>（字節(jié)）
   ③?maxmemory-policy 最大內(nèi)存緩存過期清除策略
   ? ? ?備注：
   lru:標(biāo)識(shí)最近使用的少
   生產(chǎn)中一般只建議選擇1~5的選項(xiàng)。
   ? ? ?1)volatile-lru -> 使用LRU算法移除key，只對(duì)設(shè)置了過期時(shí)間的鍵
   ? ? ?2)allkeys-lru -> 使用LRU算法移除任何key
   ? ? ?3) volatile-random -> 在過期集合中移除隨機(jī)的key，只對(duì)設(shè)置了過期時(shí)間的鍵
   ? ? ?4)allkeys-random -> 移除隨機(jī)的key
   ? ? ?5) volatile-ttl -> ?移除那些TTL值最小的key，即那些最近要過期的key
   ? ? ?6) noeviction -> 不進(jìn)行移除。針對(duì)寫操作，只是返回錯(cuò)誤信息。
   ④?maxmemory-samples 設(shè)置最大內(nèi)存樣本數(shù)量，LRU算法和最小TTL算法都并非是精確的算法，而是估算值，所以你可以設(shè)置樣本的大小，redis默認(rèn)會(huì)檢查這么多個(gè)key并選中其中LRU的那個(gè)。
   
   
   
8. 常見配置 redis.conf介紹
   
   
   
   
   
   
   
   
   

總結(jié)

以上是生活随笔為你收集整理的Redis 配置文件介绍——redis.conf的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。