admin管理员组文章数量:1646324
redis配置文件详解
- 一、常用配置项
- 二、 Redis配置文件示例。
一、常用配置项
# 参数说明redis.conf 配置项说明如下：
# 1. Redis默认不是以守护进程的方式运行，可以通过该配置项修改，使用yes启用守护进程 daemonize no
# 2. 当Redis以守护进程方式运行时，Redis默认会把pid写入/var/run/redis.pid文件，可以通过pidfile指定 pidfile /var/run/redis.pid
# 3. 指定Redis监听端口，默认端口为6379，作者在自己的一篇博文中解释了为什么选用6379作为默认端口，因为6379在手机按键上MERZ对应的号码，而MERZ取自意大利歌女Alessia Merz的名字 port 6379
# 4. 绑定的主机地址 bind 127.0.0.1
# 5. 当客户端闲置多长时间后关闭连接，如果指定为0，表示关闭该功能 timeout 300
# 6. 指定日志记录级别，Redis总共支持四个级别：debug、verbose、notice、warning，默认为verbose loglevel verbose
# 7. 日志记录方式，默认为标准输出，如果配置Redis为守护进程方式运行，而这里又配置为日志记录方式为标准输出，则日志将会发送给/dev/null logfile stdout
# 8. 设置数据库的数量，默认数据库为0，可以使用SELECT <dbid>命令在连接上指定数据库id databases 16
# 9. 指定在多长时间内，有多少次更新操作，就将数据同步到数据文件，可以多个条件配合 save <seconds> <changes> Redis默认配置文件中提供了三个条件： save 900 1 save 300 10 save 60 10000 分别表示900秒（15分钟）内有1个更改，300秒（5分钟）内有10个更改以及60秒内有10000个更改。
# 10. 指定存储至本地数据库时是否压缩数据，默认为yes，Redis采用LZF压缩，如果为了节省CPU时间，可以关闭该选项，但会导致数据库文件变的巨大 rdbcompression yes
# 11. 指定本地数据库文件名，默认值为dump.rdb dbfilename dump.rdb
# 12. 指定本地数据库存放目录 dir ./
# 13. 设置当本机为slav服务时，设置master服务的IP地址及端口，在Redis启动时，它会自动从master进行数据同步 slaveof <masterip> <masterport>
# 14. 当master服务设置了密码保护时，slav服务连接master的密码 masterauth <master-password>
# 15. 设置Redis连接密码，如果配置了连接密码，客户端在连接Redis时需要通过AUTH <password>命令提供密码，默认关闭 requirepass foobared
# 16. 设置同一时间最大客户端连接数，默认无限制，Redis可以同时打开的客户端连接数为Redis进程可以打开的最大文件描述符数，如果设置 maxclients 0，表示不作限制。当客户端连接数到达限制时，Redis会关闭新的连接并向客户端返回max number of clients reached错误信息 maxclients 128
# 17. 指定Redis最大内存限制，Redis在启动时会把数据加载到内存中，达到最大内存后，Redis会先尝试清除已到期或即将到期的Key，当此方法处理 后，仍然到达最大内存设置，将无法再进行写入操作，但仍然可以进行读取操作。Redis新的vm机制，会把Key存放内存，Value会存放在swap区 maxmemory <bytes>
# 18. 指定是否在每次更新操作后进行日志记录，Redis在默认情况下是异步的把数据写入磁盘，如果不开启，可能会在断电时导致一段时间内的数据丢失。因为 redis本身同步数据文件是按上面save条件来同步的，所以有的数据会在一段时间内只存在于内存中。默认为no appendonly no
# 19. 指定更新日志文件名，默认为appendonly.aof appendfilename appendonly.aof
# 20. 指定更新日志条件，共有3个可选值： no：表示等操作系统进行数据缓存同步到磁盘（快） always：表示每次更新操作后手动调用fsync()将数据写到磁盘（慢，安全） everysec：表示每秒同步一次（折衷，默认值） appendfsync everysec
# 21. 指定是否启用虚拟内存机制，默认值为no，简单的介绍一下，VM机制将数据分页存放，由Redis将访问量较少的页即冷数据swap到磁盘上，访问多的页面由磁盘自动换出到内存中（在后面的文章我会仔细分析Redis的VM机制） vm-enabled no
# 22. 虚拟内存文件路径，默认值为/tmp/redis.swap，不可多个Redis实例共享 vm-swap-file /tmp/redis.swap
# 23. 将所有大于vm-max-memory的数据存入虚拟内存,无论vm-max-memory设置多小,所有索引数据都是内存存储的(Redis的索引数据 就是keys),也就是说,当vm-max-memory设置为0的时候,其实是所有value都存在于磁盘。默认值为0 vm-max-memory 0
# 24. Redis swap文件分成了很多的page，一个对象可以保存在多个page上面，但一个page上不能被多个对象共享，vm-page-size是要根据存储的 数据大小来设定的，作者建议如果存储很多小对象，page大小最好设置为32或者64bytes；如果存储很大大对象，则可以使用更大的page，如果不 确定，就使用默认值 vm-page-size 32
# 25. 设置swap文件中的page数量，由于页表（一种表示页面空闲或使用的bitmap）是在放在内存中的，，在磁盘上每8个pages将消耗1byte的内存。 vm-pages 134217728
# 26. 设置访问swap文件的线程数,最好不要超过机器的核数,如果设置为0,那么所有对swap文件的操作都是串行的，可能会造成比较长时间的延迟。默认值为4 vm-max-threads 4
# 27. 设置在向客户端应答时，是否把较小的包合并为一个包发送，默认为开启 glueoutputbuf yes
# 28. 指定在超过一定的数量或者最大的元素超过某一临界值时，采用一种特殊的哈希算法 hash-max-zipmap-entries 64 hash-max-zipmap-value 512
# 29. 指定是否激活重置哈希，默认为开启（后面在介绍Redis的哈希算法时具体介绍） activerehashing yes
# 30. 指定包含其它的配置文件，可以在同一主机上多个Redis实例之间使用同一份配置文件，而同时各个实例又拥有自己的特定配置文件 include /path/to/local.conf
二、 Redis配置文件示例。
请复制到文本中查看，右侧有中文翻译
# Redis配置文件示例。
#
# Note that in order to read the configuration file, Redis must be 注意，为了读取配置文件，Redis必须是 以文件路径作为第一个参数开头：
# 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 5GB 4M格式，依此类推：
#
# 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. 单位不区分大小写，因此1GB 1Gb 1gB都相同。
################################## INCLUDES 包括 ###################################
# Include one or more other config files here. This is useful if you 在此处包含一个或多个其他配置文件。如果您具有可用于所有Redis服务器的标准模板，
# 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" 注意选项“ include”不会被命令“ CONFIG REWRITE”重写
# from admin or Redis Sentinel. Since Redis always uses the last processed 来自admin或Redis Sentinel。由于Redis总是使用最后处理的
# line as value of a configuration directive, you'd better put includes 将line作为配置指令的值，最好将include
# at the beginning of this file to avoid overwriting config change at runtime. 在此文件的开头，以避免在运行时覆盖配置更改。
#
# If instead you are interested in using includes to override configuration 如果相反，您有兴趣使用include覆盖配置
# options, it is better to use include as the last line. 选项，最好使用include作为最后一行。
#
# include /path/to/local.conf
# include /path/to/other.conf
################################## MODULES 模组 #####################################
# Load modules at startup. If the server is not able to load modules
# it will abort. It is possible to use multiple loadmodule directives. 在启动时加载模块。如果服务器无法加载模块，它将中止。可以使用多个loadmodule指令。
#
#
# loadmodule /path/to/my_module.so
# loadmodule /path/to/other_module.so
################################## NETWORK 网络 #####################################
# By default, if no "bind" configuration directive is specified, Redis listens 默认情况下，如果未指定“ bind”配置指令，则Redis侦听来自服务器上所有可用网络接口的连接。
# for connections from all the network interfaces available on the server. 可以使用“ bind”配置指令仅侦听一个或多个所选接口，然后侦听一个或多个IP地址。
# 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 ~~~警告~~~如果运行Redis的计算机直接暴露于Internet，
# internet, binding to all the interfaces is dangerous and will expose the 则绑定到所有接口都是很危险的，并且会将实例暴露给Internet上的所有人。
# instance to everybody on the internet. So by default we uncomment the 因此，默认情况下，我们取消注释遵循bind指令，这将强制Redis仅侦听IPv4环回接口地址
# following bind directive, that will force Redis to listen only into （这意味着Redis将能够仅接受来自正在运行同一台计算机的客户端的连接）。
# the IPv4 loopback 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 ::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. 保护模式是一层安全保护，以避免访问和利用Internet上打开的Redis实例。
#
# When protected mode is on and if: 当保护模式打开时，如果：
#
#
# 1) The server is not binding explicitly to a set of addresses using the
# "bind" directive. 1) 服务器未使用“ bind”指令将其显式绑定到一组地址。
# 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 该服务器仅接受来自客户端的连接，该客户端从IPv4和IPv6回送地址127.0.0.1
# sockets. 和:: 1，以及从Unix域套接字连接。
#
# By default protected mode is enabled. You should disable it only if 默认情况下启用保护模式。仅当您确定要使其他主机的客户端连接到Redis
# you are sure you want clients from other hosts to connect to Redis （即使未配置身份验证）或特定的接口集时，才应禁用它使用“ bind”指令显式列出。
# even if no authentication is configured, nor a specific set of interfaces
# are explicitly listed using the "bind" directive.
#
protected-mode no
# Accept connections on the specified port, default is 6379 (IANA #815344). 接受指定端口上的连接，默认为6379（IANA＃815344）。
# If port 0 is specified Redis will not listen on a TCP socket. 如果指定了端口0，则Redis将不会在TCP套接字上侦听。
#
port 6380
# TCP listen() backlog.
#
# In high requests-per-second environments you need an high backlog in order tcp-backlog设置tcp的backlog，backlog其实是一个连接队列，backlog
# 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 在高并发环境下你需要一个高backlog值来避免慢客户端连接问题。
# make sure to raise both the value of somaxconn and tcp_max_syn_backlog 注意Linux内核会将这个值减小到/proc/sys/net/core/somaxconn的值，
# in order to get the desired effect. 所以需要确认增大somaxconn和tcp_max_syn_backlog两个值来达到想要的效果
tcp-backlog 511
# Unix socket. Unix套接字。
#
# Specify the path for the Unix socket that will be used to listen for 指定用于侦听传入连接的Unix套接字的路径。没有默认值，因此在未指定Redis时，
# incoming connections. There is no default, so Redis will not listen Redis将不会在Unix套接字上侦听。
# on a unix socket when not specified.
#
# unixsocket /var/run/redis/redis-server.sock
# unixsocketperm 700
# Close the connection after a client is idle for N seconds (0 to disable) 客户端闲置N秒后关闭连接（0禁用）
timeout 0
# TCP keepalive. 单位为秒，如果设置为0，则不会进行Keepalive检测，建议设置成60 （集群用）
#
# If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
# of communication. This is useful for two reasons: 如果非零，请在没有通信的情况下使用SO_KEEPALIVE向客户端发送TCP ACK。这很有用，有两个原因：
#
#
#
# 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. 在Linux上，指定的值（以秒为单位）是用于发送ACK的时间段。
# 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. 此选项的合理值为300秒，这是新的Redis默认从Redis 3.2.1开始。
tcp-keepalive 300
################################# GENERAL 通用 #####################################
# By default Redis does not run as a daemon. Use 'yes' if you need it. 默认情况下，Redis不会作为守护程序运行。如果需要，请使用“是”。
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized. 请注意，Redis守护进程将在/var/run/redis.pid中写入一个pid文件。
daemonize yes
# If you run Redis from upstart or systemd, Redis can interact with your 如果从upstart或systemd运行Redis，Redis可以与您的监督树进行交互。选项：
# supervision tree. Options:
# supervised no - no supervision interaction 没有监督互动
# supervised upstart - signal upstart by putting Redis into SIGSTOP mode 通过将Redis置于SIGSTOP模式来发出信号以指示新贵
# supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET 通过将READY = 1写入$ NOTIFY_SOCKET来产生信号
# supervised auto - detect upstart or systemd method based on 根据UPSTART_JOB或NOTIFY_SOCKET环境变量检测upstart或systemd方法
# 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. 注意：这些监视方法仅表示“过程已准备就绪”。它们不能使您的主管连续不断地进行ping操作。
supervised no
# If a pid file is specified, Redis writes it where specified at startup
# and removes it at exit. 如果指定了pid文件，则Redis会在启动时将其写入指定位置，然后在退出时将其删除。
#
# When the server runs non daemonized, no pid file is created if none is 当服务器在非守护进程中运行时，如果在配置中未指定任何pid文件，
# specified in the configuration. When the server is daemonized, the pid file 则不会创建该文件。守护服务器时，即使未指定，
# is used even if not specified, defaulting to "/var/run/redis.pid". 也会使用pid文件，默认为“ /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. 尽最大努力创建一个pid文件：如果Redis无法创建它，则不会发生任何不良情况，服务器将正常启动并运行。
pidfile /var/run/redis/redis-server.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 【指定日志文件名。空字符串也可以用于强制Redis登录标准输出。
# output for logging but daemonize, logs will be sent to /dev/null 请注意，如果您使用标准输出进行日志记录但进行守护进程，则日志将发送到/ dev / null】
#
logfile /var/log/redis/redis-server.log
# To enable logging to the system logger, just set 'syslog-enabled' to yes, 【要启用到系统记录器的日志记录，只需将“ syslog-enabled”设置为yes，
# and optionally update the other syslog parameters to suit your needs. 并根据需要更新其他syslog参数。】
#
syslog-enabled yes
# Specify the syslog identity. 指定系统日志标识。
# syslog-ident redis
# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7. 指定系统日志工具。必须是USER或LOCAL0-LOCAL7之间。
# syslog-facility local0
# Set the number of databases. The default database is DB 0, you can select 【设置数据库数。默认数据库是DB 0，可以选择
# a different one on a per-connection basis using SELECT <dbid> where 使用SELECT <dbid>在每个连接的基础上不同 dbid是介于0和'databases'-1之间的数字】
# dbid is a number between 0 and 'databases'-1
#
databases 16
# By default Redis shows an ASCII art logo only when started to log to the
# standard output and if the standard output is a TTY. Basically this means
# that normally a logo is displayed only in interactive sessions.
#
# However it is possible to force the pre-4.0 behavior and always show a
# ASCII art logo in startup logs by setting the following option to yes.
always-show-logo yes
################################ 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 ""
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 默认情况下，如果启用了RDB快照（至少一个保存点）并且最新的后台保存失败，Redis将停止接受写入。
# disaster will happen. 这将使用户（以一种困难的方式）意识到数据无法正确地持久存储在磁盘上，否则，可能没人会注意到并且会发生一些灾难。
#
# If the background saving process will start working again Redis will 如果后台保存过程将再次开始工作，则Redis将自动允许再次写入。
# automatically allow writes again.
#
# However if you have setup your proper monitoring of the Redis server 但是，如果您设置了对Redis服务器和持久性的适当监视，则可能要禁用此功能，
# and persistence, you may want to disable this feature so that Redis will 以便即使磁盘，权限等出现问题，Redis仍将继续照常工作。
# 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? 转储.rdb数据库时使用LZF压缩字符串对象？默认情况下将其设置为“是”，
# For default that's set to 'yes' as it's almost always a win. 因为它几乎总是胜利。如果要在保存子项中保存一些CPU，请将其设置为“ no”，
# 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 # 是否压缩.edb 文件 ，cpu 性能 和 磁盘空间做选择
# Since version 5 of RDB a CRC64 checksum is placed at the end of the file. 从RDB版本5开始，在文件末尾放置了CRC64校验和。这使该格式更能抵抗损坏，
# This makes the format more resistant to corruption but there is a performance 但是在保存和加载RDB文件时会付出一定的性能损失（大约10％），因此可以禁用该格式以获得最佳性能。
# 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 在禁用校验和的情况下创建的RDB文件的校验和为零，这将指示加载代码跳过该校验。
# tell the loading code to skip the check.
rdbchecksum yes # CRC64 校验 影响cpu性能，但是推荐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 数据库将被写入该目录内，文件名使用“ dbfilename”配置指令在上面指定。
# 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 /var/lib/redis
################################# REPLICATION 复制 #################################
# Master-Replica replication. Use replicaof to make a Redis instance a copy of
# another Redis server. A few things to understand ASAP about Redis replication.
#
# +------------------+ +---------------+
# | Master | ---> | Replica |
# | (receive writes) | | (exact copy) |
# +------------------+ +---------------+
#
# 1) Redis replication is asynchronous, but you can configure a master to
# stop accepting writes if it appears to be not connected with at least
# a given number of replicas.
# 2) Redis replicas are able to perform a partial resynchronization with the
# master if the replication link is lost for a relatively small amount of
# time. You may want to configure the replication backlog size (see the next
# sections of this file) with a sensible value depending on your needs.
# 3) Replication is automatic and does not need user intervention. After a
# network partition replicas automatically try to reconnect to masters
# and resynchronize with them.
#
# replicaof <masterip> <masterport>
# If the master is password protected (using the "requirepass" configuration
# directive below) it is possible to tell the replica to authenticate before
# starting the replication synchronization process, otherwise the master will
# refuse the replica request.
#
# masterauth <master-password>
# When a replica loses its connection with the master, or when the replication
# is still in progress, the replica can act in two different ways:
#
# 1) if replica-serve-stale-data is set to 'yes' (the default) the replica will
# still reply to client requests, possibly with out of date data, or the
# data set may just be empty if this is the first synchronization.
#
# 2) if replica-serve-stale-data is set to 'no' the replica will reply with
# an error "SYNC with master in progress" to all the kind of commands
# but to INFO, replicaOF, AUTH, PING, SHUTDOWN, REPLCONF, ROLE, CONFIG,
# SUBSCRIBE, UNSUBSCRIBE, PSUBSCRIBE, PUNSUBSCRIBE, PUBLISH, PUBSUB,
# COMMAND, POST, HOST: and LATENCY.
#
replica-serve-stale-data yes
# You can configure a replica instance to accept writes or not. Writing against
# a replica instance may be useful to store some ephemeral data (because data
# written on a replica will be easily deleted after resync with the master) but
# may also cause problems if clients are writing to it because of a
# misconfiguration.
#
# Since Redis 2.6 by default replicas are read-only.
#
# Note: read only replicas are not designed to be exposed to untrusted clients
# on the internet. It's just a protection layer against misuse of the instance.
# Still a read only replica exports by default all the administrative commands
# such as CONFIG, DEBUG, and so forth. To a limited extent you can improve
# security of read only replicas using 'rename-command' to shadow all the
# administrative / dangerous commands.
replica-read-only yes
# Replication SYNC strategy: disk or socket.
#
# -------------------------------------------------------
# WARNING: DISKLESS REPLICATION IS EXPERIMENTAL CURRENTLY
# -------------------------------------------------------
#
# New replicas and reconnecting replicas that are not able to continue the replication
# process just receiving differences, need to do what is called a "full
# synchronization". An RDB file is transmitted from the master to the replicas.
# The transmission can happen in two different ways:
#
# 1) Disk-backed: The Redis master creates a new process that writes the RDB
# file on disk. Later the file is transferred by the parent
# process to the replicas incrementally.
# 2) Diskless: The Redis master creates a new process that directly writes the
# RDB file to replica sockets, without touching the disk at all.
#
# With disk-backed replication, while the RDB file is generated, more replicas
# can be queued and served with the RDB file as soon as the current child producing
# the RDB file finishes its work. With diskless replication instead once
# the transfer starts, new replicas arriving will be queued and a new transfer
# will start when the current one terminates.
#
# When diskless replication is used, the master waits a configurable amount of
# time (in seconds) before starting the transfer in the hope that multiple replicas
# will arrive and the transfer can be parallelized.
#
# With slow disks and fast (large bandwidth) networks, diskless replication
# works better.
repl-diskless-sync no
# When diskless replication is enabled, it is possible to configure the delay
# the server waits in order to spawn the child that transfers the RDB via socket
# to the replicas.
#
# This is important since once the transfer starts, it is not possible to serve
# new replicas arriving, that will be queued for the next RDB transfer, so the server
# waits a delay in order to let more replicas arrive.
#
# The delay is specified in seconds, and by default is 5 seconds. To disable
# it entirely just set it to 0 seconds and the transfer will start ASAP.
repl-diskless-sync-delay 5
# Replicas send PINGs to server in a predefined interval. It's possible to change
# this interval with the repl_ping_replica_period option. The default value is 10
# seconds.
#
# repl-ping-replica-period 10
# The following option sets the replication timeout for:
#
# 1) Bulk transfer I/O during SYNC, from the point of view of replica.
# 2) Master timeout from the point of view of replicas (data, pings).
# 3) Replica timeout from the point of view of masters (REPLCONF ACK pings).
#
# It is important to make sure that this value is greater than the value
# specified for repl-ping-replica-period otherwise a timeout will be detected
# every time there is low traffic between the master and the replica.
#
# repl-timeout 60
# Disable TCP_NODELAY on the replica socket after SYNC?
#
# If you select "yes" Redis will use a smaller number of TCP packets and
# less bandwidth to send data to replicas. But this can add a delay for
# the data to appear on the replica side, up to 40 milliseconds with
# Linux kernels using a default configuration.
#
# If you select "no" the delay for data to appear on the replica side will
# be reduced but more bandwidth will be used for replication.
#
# By default we optimize for low latency, but in very high traffic conditions
# or when the master and replicas are many hops away, turning this to "yes" may
# be a good idea.
repl-disable-tcp-nodelay no
# Set the replication backlog size. The backlog is a buffer that accumulates
# replica data when replicas are disconnected for some time, so that when a replica
# wants to reconnect again, often a full resync is not needed, but a partial
# resync is enough, just passing the portion of data the replica missed while
# disconnected.
#
# The bigger the replication backlog, the longer the time the replica can be
# disconnected and later be able to perform a partial resynchronization.
#
# The backlog is only allocated once there is at least a replica connected.
#
# repl-backlog-size 1mb
# After a master has no longer connected replicas for some time, the backlog
# will be freed. The following option configures the amount of seconds that
# need to elapse, starting from the time the last replica disconnected, for
# the backlog buffer to be freed.
#
# Note that replicas never free the backlog for timeout, since they may be
# promoted to masters later, and should be able to correctly "partially
# resynchronize" with the replicas: hence they should always accumulate backlog.
#
# A value of 0 means to never release the backlog.
#
# repl-backlog-ttl 3600
# The replica priority is an integer number published by Redis in the INFO output.
# It is used by Redis Sentinel in order to select a replica to promote into a
# master if the master is no longer working correctly.
#
# A replica with a low priority number is considered better for promotion, so
# for instance if there are three replicas with priority 10, 100, 25 Sentinel will
# pick the one with priority 10, that is the lowest.
#
# However a special priority of 0 marks the replica as not able to perform the
# role of master, so a replica with priority of 0 will never be selected by
# Redis Sentinel for promotion.
#
# By default the priority is 100.
replica-priority 100
# It is possible for a master to stop accepting writes if there are less than
# N replicas connected, having a lag less or equal than M seconds.
#
# The N replicas need to be in "online" state.
#
# The lag in seconds, that must be <= the specified value, is calculated from
# the last ping received from the replica, that is usually sent every second.
#
# 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 replicas
# are available, to the specified number of seconds.
#
# For example to require at least 3 replicas with a lag <= 10 seconds use:
#
# min-replicas-to-write 3
# min-replicas-max-lag 10
#
# Setting one or the other to 0 disables the feature.
#
# By default min-replicas-to-write is set to 0 (feature disabled) and
# min-replicas-max-lag is set to 10.
# A Redis master is able to list the address and port of the attached
# replicas in different ways. For example the "INFO replication" section
# offers this information, which is used, among other tools, by
# Redis Sentinel in order to discover replica instances.
# Another place where this info is available is in the output of the
# "ROLE" command of a master.
#
# The listed IP and address normally reported by a replica is obtained
# in the following way:
#
# IP: The address is auto detected by checking the peer address
# of the socket used by the replica to connect with the master.
#
# Port: The port is communicated by the replica during the replication
# handshake, and is normally the port that the replica is using to
# listen for connections.
#
# However when port forwarding or Network Address Translation (NAT) is
# used, the replica may be actually reachable via different IP and port
# pairs. The following two options can be used by a replica in order to
# report to its master a specific set of IP and port, so that both INFO
# and ROLE will report those values.
#
# There is no need to use both the options if you need to override just
# the port or the IP address.
#
# replica-announce-ip 5.5.5.5
# replica-announce-port 1234
################################## 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. 【要求客户端在处理其他任何内容之前发出AUTH <PASSWORD> 条命令。这在您不信任的环境中可能很有用其他有权访问运行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 【警告：由于Redis速度非常快，外部用户可以尝试一个好的盒子每秒可输入150k密码。这意味着您应该使用非常强的密码，否则将很容易破解。】
# 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. 可以通过 config set requirepass 命令设置密码
#
# 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 replicas may cause problems.
################################### CLIENTS 客户 ####################################
# 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 许指定的限制允许的最大客户端数设置为当前文件限制减32（因为Redis保留了一些文件描述符供内部使用）。】
# minus 32 (as Redis reserves a few file descriptors for internal uses). 【＃设置同时连接的最大客户端数。默认此限制设置为10000个客户端，但是如果Redis服务器不是能够配置进程文件限制以允
#
#
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'. 【一旦达到限制，Redis将关闭所有新发送的连接错误“达到最大客户端数”。】
#
#
# maxclients 10000
############################## MEMORY MANAGEMENT 内存管理 ################################
# Set a memory usage limit to 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). 当达到内存限制时，Redis将尝试删除密钥根据选择的驱逐策略（请参阅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 如果Redis无法根据策略删除key，或者策略为设置为'noeviction'，
# to reply to read-only commands like GET. Redis将无法使用更多的内存将开始回复命令错误，例如SET，LPUSH等，并将继续回复诸如GET之类的只读命令。
#
# This option is usually useful when using Redis as an LRU or LFU cache,
# or to set a hard memory limit for an instance (using the 'noeviction' policy). 当将Redis用作LRU或LFU缓存，或为实例设置硬盘限制（使用'noeviction'策略）时，此选项通常很有用。
#
#
# WARNING: If you have replicas attached to an instance with maxmemory on,
# the size of the output buffers needed to feed the replicas 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 警告：如果您将副本附加到实例上且启用了 maxmemory ，则会从使用的内存数量中减去提供副本所需的输出缓冲区的大小，
# buffer of replicas is full with DELs of keys evicted triggering the deletion 因此网络问题/重新同步不会触发回收键的循环，反过来，副本的输出缓冲区中充满了被逐出的键DEL，
# of more keys, and so forth until the database is completely emptied. 触发了更多键的删除操作，依此类推，直到数据库完全清空。
#
# In short... if you have replicas attached it is suggested that you set a lower
# limit for maxmemory so that there is some free RAM on the system for replica 简而言之...如果您附加了副本，建议您为maxmemory设置一个下限，
# output buffers (but this is not needed if the policy is 'noeviction'). 以便系统上有一些可用RAM用于副本输出缓冲区（但是如果策略为'noeviction'，则不需要这样做）。
#
#
# maxmemory <bytes>
maxmemory 512mb
#
# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
# is reached. You can select among five behaviors:
# MAXMEMORY POLICY： 达到maxmemory后，Redis将如何选择要删除的内容。您可以选择以下五种行为：
#
# volatile-lru -> Evict using approximated LRU among the keys with an expire set. 使用LRU算法移除key，只对设置了过期时间的键
# allkeys-lru -> Evict any key using approximated LRU. 使用LRU算法移除key
# volatile-lfu -> Evict using approximated LFU among the keys with an expire set. 在过期集合中移除随机的key，只对设置了过期时间的键
# allkeys-lfu -> Evict any key using approximated LFU. 使用LFU算法移除key
# volatile-random -> Remove a random key among the ones with an expire set. 从设置了过期设置的key中随机删除。
# allkeys-random -> Remove a random key, any key. 删除随机key。
# volatile-ttl -> Remove the key with the nearest expire time (minor TTL) 移除那些TTL值最小的key，即那些最近要过期的key
# noeviction -> Don't evict anything, just return an error on write operations. 不进行移除。针对写操作，只是返回错误信息
#
# LRU means Least Recently Used 表示最近最少使用
# LFU means Least Frequently Used 表示最少使用
#
# Both LRU, LFU and volatile-ttl are implemented using approximated
# randomized algorithms. LRU，LFU和volatile-ttl均使用近似随机算法实现。
#
# Note: with any of the above policies, Redis will return an error on write
# operations, when there are no suitable keys for eviction. 注意：使用上述任何策略时，如果没有合适的退出键，Redis将在写入操作中返回错误。
#
# 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, LFU and minimal TTL algorithms are not precise algorithms but approximated LRU，LFU和最小TTL算法不是精确算法，而是近似算法（以节省内存），
# 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 Redis将检查五个键并选择最近使用的键，您可以使用以下配置指令更改样本大小。
# 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 默认值5会产生足够好的结果。 10非常接近真实的LRU，
# true LRU but costs more CPU. 3 is faster but not very accurate. 但是会花费更多的CPU。 3更快，但不是很准确。
#
# maxmemory-samples 5
# Starting from Redis 5, by default a replica will ignore its maxmemory setting 从Redis 5开始，默认情况下，副本将忽略其maxmemory设置（除非在故障转移后或手动提升为主副本）。
# (unless it is promoted to master after a failover or manually). It means 这意味着key的移出将仅由主机处理，将移除命令由主机侧发出到副本。
# that the eviction of keys will be just handled by the master, sending the
# DEL commands to the replica as keys evict in the master side.
#
# This behavior ensures that masters and replicas stay consistent, and is usually 此行为可确保母版和副本保持一致，这通常是您想要的，
# what you want, however if your replica is writable, or you want the replica to have 但是，如果副本是可写的，或者您希望副本具有不同的内存设置，
# a different memory setting, and you are sure all the writes performed to the 并且您确定对副本执行的所有写操作都是幂等的，那么您可以更改此默认设置（但请务必了解您的操作）。
# replica are idempotent, then you may change this default (but be sure to understand
# what you are doing).
#
# Note that since the replica by default does not evict, it may end using more 请注意，由于默认情况下该副本不会退出，因此它可能会使用比通过maxmemory设置的内存更多的内存
# memory than the one set via maxmemory (there are certain buffers that may （某些缓冲区在副本上可能会更大，或者数据结构有时会占用更多内存等等）。
# be larger on the replica, or data structures may sometimes take more memory and so 因此，请确保您监视副本并确保副本具有足够的内存，
# forth). So make sure you monitor your replicas and make sure they have enough 以确保在主副本达到配置的最大内存设置之前，副本永远不会达到实际的内存不足状态。
# memory to never hit a real out-of-memory condition before the master hits
# the configured maxmemory setting.
#
# replica-ignore-maxmemory yes 复制副本忽略最大内存 yes
############################# LAZY FREEING 懒惰释放####################################
# Redis has two primitives to delete keys. One is called DEL and is a blocking Redis有两个删除键的原语。一种称为DEL，它是对象的阻塞删除。
# deletion of the object. It means that the server stops processing new commands 这意味着服务器停止处理新命令，以便以同步方式回收与对象关联的所有内存。
# in order to reclaim all the memory associated with an object in a synchronous 如果删除的键与一个小对象相关联，则执行DEL命令所需的时间非常短，
# way. If the key deleted is associated with a small object, the time needed 可与Redis中的大多数其他O（1）或O（log_N）命令相提并论。
# in order to execute the DEL command is very small and comparable to most other 但是，如果键与包含数百万个元素的聚合值相关联，则服务器可能会阻塞很长时间（甚至几秒钟）以完成操作。
# O(1) or O(log_N) commands in Redis. However if the key is associated with an
# aggregated value containing millions of elements, the server can block for
# a long time (even seconds) in order to complete the operation.
#
# For the above reasons Redis also offers non blocking deletion primitives 由于上述原因，Redis还提供了非阻塞删除原语，例如UNLINK（非阻塞DEL）以及FLUSHALL和FLUSHDB命令的ASYNC选项，
# such as UNLINK (non blocking DEL) and the ASYNC option of FLUSHALL and 以便在后台回收内存。这些命令在固定时间内执行。另一个线程将尽可能快地在后台逐渐释放对象。
# FLUSHDB commands, in order to reclaim memory in background. Those commands
# are executed in constant time. Another thread will incrementally free the
# object in the background as fast as possible.
#
# DEL, UNLINK and ASYNC option of FLUSHALL and FLUSHDB are user-controlled. 用户可以控制FLUSHALL和FLUSHDB的DEL，UNLINK和ASYNC选项。由应用程序的设计决定何时使用一个或另一个是一个好主意。
# It's up to the design of the application to understand when it is a good 但是，Redis服务器有时必须删除键或刷新整个数据库，这是其他操作的副作用。特别是在以下情况下，Redis独立于用户调用删除对象：
# idea to use one or the other. However the Redis server sometimes has to
# delete keys or flush the whole database as a side effect of other operations.
# Specifically Redis deletes objects independently of a user call in the
# following scenarios:
#
# 1) On eviction, because of the maxmemory and maxmemory policy configurations,
# in order to make room for new data, without going over the specified
# memory limit. 逐出时，由于maxmemory和maxmemory策略配置，以便在不超过指定的内存限制的情况下为新数据腾出空间。
# 2) Because of expire: when a key with an associated time to live (see the 因为到期：必须从内存中删除具有相关生存时间的密钥（请参阅EXPIRE命令）。
# EXPIRE command) must be deleted from memory.
# 3) Because of a side effect of a command that stores data on a key that may 由于将数据存储在可能已经存在的键上的命令的副作用。例如，当RENAME命令被另一旧密钥内容替换时，
# already exist. For example the RENAME command may delete the old key 它可能会删除它。同样，SUNIONSTORE或SORT with STORE选项可能会删除现有密钥。
# content when it is replaced with another one. Similarly SUNIONSTORE SET命令本身会删除指定键的所有旧内容，以便将其替换为指定的字符串。
# or SORT with STORE option may delete existing keys. The SET command
# itself removes any old content of the specified key in order to replace
# it with the specified string.
# 4) During replication, when a replica performs a full resynchronization with 复制期间，当副本与其主副本执行完全重新同步时，将删除整个数据库的内容，以便加载刚传输的RDB文件。
# its master, the content of the whole database is removed in order to
# load the RDB file just transferred.
#
# In all the above cases the default is to delete objects in a blocking way, 在上述所有情况下，默认设置都是以阻塞方式删除对象，就像调用DEL一样。但是，
# like if DEL was called. However you can configure each case specifically 您可以专门配置每种情况，以便使用以下配置指令以非阻塞方式释放内存，例如调用UNLINK的情况：
# in order to instead release memory in a non-blocking way like if UNLINK
# was called, using the following configuration directives:
lazyfree-lazy-eviction no
lazyfree-lazy-expire no
lazyfree-lazy-server-del no
replica-lazy-flush no
############################## APPEND ONLY MODE 追加模式 ###############################
# By default Redis asynchronously dumps the dataset on disk. This mode is 默认情况下，Redis异步将数据集转储到磁盘上。此模式在许多应用程序中已经足够好，
# good enough in many applications, but an issue with the Redis process or 但是Redis进程问题或停电可能会导致几分钟的写入丢失（取决于配置的保存点）。
# a power outage may result into a few minutes of writes lost (depending on
# the configured save points).
#
# The Append Only File is an alternative persistence mode that provides 仅附加文件是一种替代的持久性模式，可提供更好的持久性。
# much better durability. For instance using the default data fsync policy 例如，使用默认的数据fsync策略（请参阅配置文件中的稍后内容），Redis在严重的事件（例如服务器断电）中可能仅损失一秒钟的写操作，
# (see later in the config file) Redis can lose just one second of writes in a 如果Redis进程本身发生了问题，则可能丢失一次写操作，但是操作系统仍在正常运行。
# dramatic event like a server power outage, or a single write if something
# wrong with the Redis process itself happens, but the operating system is
# still running correctly.
#
# AOF and RDB persistence can be enabled at the same time without problems. 可以同时启用AOF和RDB持久性，而不会出现问题。如果在启动时启用了AOF，则Redis将加载AOF，即该文件具有更好的持久性保证。
# If the AOF is enabled on startup Redis will load the AOF, that is the file
# with the better durability guarantees.
#
# Please check http://redis.io/topics/persistence for more information.
appendonly yes
# The name of the append only file (default: "appendonly.aof") 仅附加文件的名称（默认值：“ appendonly.aof”）
appendfilename "appendonly.aof"
# The fsync() call tells the Operating System to actually write data on disk fsync（）命令调用告诉操作系统将数据实际写入磁盘，而不是等待输出缓冲区中的更多数据。
# instead of waiting 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: Redis支持三种不同的模式：
#
# no: don't fsync, just let the OS flush the data when it wants. Faster. no：不要fsync，只要让OS在需要时刷新数据即可。快点。
# always: fsync after every write to the append only log. Slow, Safest. always： 每次写入仅附加日志后，执行fsync。慢，最安全。
# everysec: fsync only one time every second. Compromise. everysec：每秒仅同步一次fsync。适中
#
# The default is "everysec", as that's usually the right compromise between 默认值为“ everysec”，因为这通常是速度和数据安全性之间的正确折衷。
# speed and data safety. It's up to you to understand if you can relax this to （但如您可以了解是否可以将其放宽为“ no”，以便操作系统在需要时刷新输出缓冲区，以获得更好的性能
# "no" that will let the operating system flush the output buffer when 果您可以忍受某些数据丢失的想法，请考虑使用默认的持久性模式（即快照），或者相反，
# it wants, for better performances (but if you can live with the idea of 请使用“总是”，该速度非常慢，但比securesec更安全。
# some data loss consider the default persistence mode that's snapshotting),
# or on the contrary, use "always" that's very slow but a bit safer than
# everysec.
#
# More details please check the following article:
# http://antirez/post/redis-persistence-demystified.html
#
# If unsure, use "everysec". 如果不确定，请使用“ everysec”。
# appendfsync always
appendfsync everysec
# appendfsync no
# When the AOF fsync policy is set to always or everysec, and a background 当AOF fsync策略设置为always或everysec，并且后台保存进程（后台保存或AOF日志后台重写）
# saving process (a background save or AOF log background rewriting) is 对磁盘执行大量I / O时，在某些Linux配置中，Redis可能会阻塞太长时间fsync（）调用。
# performing a lot of I/O against the disk, in some Linux configurations 请注意，目前尚无此修复程序，因为即使在其他线程中执行fsync也将阻塞我们的同步write（2）调用。
# Redis may block too long on the fsync() call. Note that there is no fix for
# this currently, as even performing fsync in a different thread will block
# our synchronous write(2) call.
#
# In order to mitigate this problem it's possible to use the following option 为了减轻此问题，可以使用以下选项来防止在 BGSAVE 或 BGREWRITEAOF 进行时在主进程中调用fsync（）。
# that will prevent fsync() from being called in the main process while a
# BGSAVE or BGREWRITEAOF is in progress.
#
# This means that while another child is saving, the durability of Redis is 这意味着当另一个子进程正在保存时，Redis的持久性与“ appendfsync none”相同。
# the same as "appendfsync none". In practical terms, this means that it is 实际上，这意味着在最坏的情况下（使用默认的Linux设置）可能会丢失多达30秒的日志。
# possible to lose up to 30 seconds of log in the worst scenario (with the
# default Linux settings).
#
# If you have latency problems turn this to "yes". Otherwise leave it as 如果您有延迟问题，请将其设置为“是”。否则，从耐用性的角度来看，这是最安全的选择。
# "no" that is the safest pick from the point of view of durability.
no-appendfsync-on-rewrite no
# Automatic rewrite of the append only file. 自动重写仅附加文件。当AOF日志大小增加指定的百分比时，Redis可以自动重写日志文件，隐式调用BGREWRITEAOF。
# Redis is able to automatically rewrite the log file implicitly calling
# BGREWRITEAOF when the AOF log size grows by the specified percentage.
#
# This is how it works: Redis remembers the size of the AOF file after the 它是这样工作的：Redis会在最近一次重写后记住AOF文件的大小（如果自重新启动以来未发生任何重写，则使用启动时AOF的大小）。
# latest rewrite (if no rewrite has happened since the restart, the size of
# the AOF at startup is used).
#
# This base size is compared to the current size. If the current size is 将此基本大小与当前大小进行比较。如果当前大小大于指定的百分比，则触发重写。
# bigger than the specified percentage, the rewrite is triggered. Also 另外，您需要指定要重写的AOF文件的最小大小，这对于避免重写AOF文件很有用，即使达到百分比增加但它仍然很小。
# you need to specify a minimal size for the AOF file to be rewritten, this
# is useful to avoid rewriting the AOF file even if the percentage increase
# is reached but it is still pretty small.
#
# Specify a percentage of zero in order to disable the automatic AOF rewrite feature. 指定零百分比以禁用自动AOF重写功能。
auto-aof-rewrite-percentage 100 # 默认比上次保存文件大1倍
auto-aof-rewrite-min-size 64mb # 当文件大于64mb是才会出发重写，生产环境一般几个G
# An AOF file may be found to be truncated at the end during the Redis 当AOF数据重新加载到内存中时，在Redis启动过程中可能会发现AOF文件在末尾被截断。
# startup process, when the AOF data gets loaded back into memory. 当运行Redis的系统崩溃时，尤其是在没有data = ordered选项的情况下挂载ext4文件系统时，
# This may happen when the system where Redis is running 可能会发生这种情况（但是，当Redis本身崩溃或中止，但操作
# crashes, especially when an ext4 filesystem is mounted without the 系统仍然可以正常运行时，就不会发生这种情况）。
# data=ordered option (however this can't happen when Redis itself
# crashes or aborts but the operating system still works correctly).
#
# Redis can either exit with an error when this happens, or load as much 发生这种情况时，Redis可以退出并显示错误，也可以加载尽可能多的数据（当前为默认值），
# data as possible (the default now) and start if the AOF file is found 如果发现AOF文件最后被截断，则Redis可以启动。以下选项控制此行为。
# to be truncated at the end. The following option controls this behavior.
#
# If aof-load-truncated is set to yes, a truncated AOF file is loaded and 如果aof-load-truncated设置为yes，则将加载截短的AOF文件，
# the Redis server starts emitting a log to inform the user of the event. 并且Redis服务器将开始发出日志以将事件通知用户。
# Otherwise if the option is set to no, the server aborts with an error 否则，如果该选项设置为no，则服务器将中止并显示错误并拒绝启动。
# and refuses to start. When the option is set to no, the user requires 如果该选项设置为no，则用户需要在重新启动服务器之前使用“ redis-check-aof”实用程序修复AOF文件。
# to fix the AOF file using the "redis-check-aof" utility before to restart
# the server.
#
# Note that if the AOF file will be found to be corrupted in the middle 请注意，如果在中间发现AOF文件已损坏，则服务器仍将退出并出现错误。
# the server will still exit with an error. This option only applies when 仅当Redis尝试从AOF文件读取更多数据但找不到足够的字节时，此选项才适用
# Redis will try to read more data from the AOF file but not enough bytes
# will be found.
aof-load-truncated yes
# When rewriting the AOF file, Redis is able to use an RDB preamble in the 重写AOF文件时，Redis可以使用AOF文件中的RDB前同步码来更快地进行重写和恢复。
# AOF file for faster rewrites and recoveries. When this option is turned 启用此选项后，重写的AOF文件由两个不同的节组成：
# on the rewritten AOF file is composed of two different stanzas:
#
# [RDB file][AOF tail] [RDB文件] [AOF尾巴]
#
# When loading Redis recognizes that the AOF file starts with the "REDIS" 加载时，Redis会识别AOF文件以“ REDIS”字符串开头并加载带前缀的RDB文件，然后继续加载AOF尾部。
# string and loads the prefixed RDB file, and continues loading the AOF
# tail.
aof-use-rdb-preamble yes
################################ LUA SCRIPTING LUA 脚本###############################
# Max execution time of a Lua script in milliseconds.
#
# If the maximum execution time is reached Redis will log that a script is
# still in execution after the maximum allowed time and will start to
# reply to queries with an error.
#
# When a long running script exceeds 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 was
# already issued by the script but the user doesn't want to wait for the natural
# termination of the script.
#
# Set it to 0 or a negative value for unlimited execution without warnings.
lua-time-limit 5000
################################ REDIS CLUSTER REDIS 集群 ###############################
# Normal Redis instances can't be part of a Redis Cluster; only nodes that are
# started as cluster nodes can. In order to start a Redis instance as a
# cluster node enable the cluster support uncommenting the following:
#
# cluster-enabled yes
# 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 not have
# overlapping cluster configuration file names.
#
# cluster-config-file nodes-6379.conf
# Cluster node timeout is the amount of milliseconds a node must be unreachable
# for it to be considered in failure state.
# Most other internal time limits are multiple of the node timeout.
#
# cluster-node-timeout 15000
# A replica of a failing master will avoid to start a failover if its data
# looks too old.
#
# There is no simple way for a replica to actually have an exact measure of
# its "data age", so the following two checks are performed:
#
# 1) If there are multiple replicas able to failover, they exchange messages
# in order to try to give an advantage to the replica with the best
# replication offset (more data from the master processed).
# Replicas will try to get their rank by offset, and apply to the start
# of the failover a delay proportional to their rank.
#
# 2) Every single replica computes the time of the last interaction with
# its master. This can be the last ping or command received (if the master
# is still in the "connected" state), or the time that elapsed since the
# disconnection with the master (if the replication link is currently down).
# If the last interaction is too old, the replica will not try to failover
# at all.
#
# The point "2" can be tuned by user. Specifically a replica will not perform
# the failover if, since the last interaction with the master, the time
# elapsed is greater than:
#
# (node-timeout * replica-validity-factor) + repl-ping-replica-period
#
# So for example if node-timeout is 30 seconds, and the replica-validity-factor
# is 10, and assuming a default repl-ping-replica-period of 10 seconds, the
# replica will not try to failover if it was not able to talk with the master
# for longer than 310 seconds.
#
# A large replica-validity-factor may allow replicas with too old data to failover
# a master, while a too small value may prevent the cluster from being able to
# elect a replica at all.
#
# For maximum availability, it is possible to set the replica-validity-factor
# to a value of 0, which means, that replicas will always try to failover the
# master regardless of the last time they interacted with the master.
# (However they'll always try to apply a delay proportional to their
# offset rank).
#
# Zero is the only value able to guarantee that when all the partitions heal
# the cluster will always be able to continue.
#
# cluster-replica-validity-factor 10
# Cluster replicas are able to migrate to orphaned masters, that are masters
# that are left without working replicas. This improves the cluster ability
# to resist to failures as otherwise an orphaned master can't be failed over
# in case of failure if it has no working replicas.
#
# Replicas migrate to orphaned masters only if there are still at least a
# given number of other working replicas for their old master. This number
# is the "migration barrier". A migration barrier of 1 means that a replica
# will migrate only if there is at least 1 other working replica for its master
# and so forth. It usually reflects the number of replicas you want for every
# master in your cluster.
#
# Default is 1 (replicas migrate only if their masters remain with at least
# one replica). To disable migration just set it to a very large value.
# A value of 0 can be set but is useful only for debugging and dangerous
# in production.
#
# cluster-migration-barrier 1
# By default Redis Cluster nodes stop accepting queries if they detect there
# is at least an hash slot uncovered (no available node is serving it).
# This way if the cluster is partially down (for example a range of hash slots
# are no longer covered) all the cluster becomes, eventually, unavailable.
# It automatically returns available as soon as all the slots are covered again.
#
# However sometimes you want the subset of the cluster which is working,
# to continue to accept queries for the part of the key space that is still
# covered. In order to do so, just set the cluster-require-full-coverage
# option to no.
#
# cluster-require-full-coverage yes
# This option, when set to yes, prevents replicas from trying to failover its
# master during master failures. However the master can still perform a
# manual failover, if forced to do so.
#
# This is useful in different scenarios, especially in the case of multiple
# data center operations, where we want one side to never be promoted if not
# in the case of a total DC failure.
#
# cluster-replica-no-failover no
# In order to setup your cluster make sure to read the documentation
# available at http://redis.io web site.
########################## CLUSTER DOCKER/NAT support 集群DOCKER / NAT支持 ########################
# In certain deployments, Redis Cluster nodes address discovery fails, because
# addresses are NAT-ted or because ports are forwarded (the typical case is
# Docker and other containers).
#
# In order to make Redis Cluster working in such environments, a static
# configuration where each node knows its public address is needed. The
# following two options are used for this scope, and are:
#
# * cluster-announce-ip
# * cluster-announce-port
# * cluster-announce-bus-port
#
# Each instruct the node about its address, client port, and cluster message
# bus port. The information is then published in the header of the bus packets
# so that other nodes will be able to correctly map the address of the node
# publishing the information.
#
# If the above options are not used, the normal Redis Cluster auto-detection
# will be used instead.
#
# Note that when remapped, the bus port may not be at the fixed offset of
# clients port + 10000, so you can specify any port and bus-port depending
# on how they get remapped. If the bus-port is not set, a fixed offset of
# 10000 will be used as usually.
#
# Example:
#
# cluster-announce-ip 10.1.1.5
# cluster-announce-port 6379
# cluster-announce-bus-port 6380
################################## SLOW LOG 慢日志###################################
# The Redis Slow Log is a system to log queries that exceeded a specified
# execution time. The execution time does not include the I/O operations
# like talking with the client, sending the reply and so forth,
# but just the time needed to actually execute the command (this is the only
# stage of command execution where the thread is blocked and can not serve
# other requests in the meantime).
#
# You can configure the slow log with two parameters: one tells Redis
# what is the execution time, in microseconds, to exceed in order for the
# command to get logged, and the other parameter is the length of the
# slow log. When a new command is logged the oldest one is removed from the
# queue of logged commands.
# The following time is expressed in microseconds, so 1000000 is equivalent
# to one second. Note that a negative number disables the slow log, while
# a value of zero forces the logging of every command.
slowlog-log-slower-than 10000
# There is no limit to this length. Just be aware that it will consume memory.
# You can reclaim memory used by the slow log with SLOWLOG RESET.
slowlog-max-len 128
################################ LATENCY MONITOR 延迟监视器##############################
# The Redis latency monitoring subsystem samples different operations
# at runtime in order to collect data related to possible sources of
# latency of a Redis instance.
#
# Via the LATENCY command this information is available to the user that can
# print graphs and obtain reports.
#
# The system only logs operations that were performed in a time equal or
# greater than the amount of milliseconds specified via the
# latency-monitor-threshold configuration directive. When its value is set
# to zero, the latency monitor is turned off.
#
# By default latency monitoring is disabled since it is mostly not needed
# if you don't have latency issues, and collecting data has a performance
# impact, that while very small, can be measured under big load. Latency
# monitoring can easily be enabled at runtime using the command
# "CONFIG SET latency-monitor-threshold <milliseconds>" if needed.
latency-monitor-threshold 0
############################# EVENT NOTIFICATION 活动通知 ##############################
# Redis can notify Pub/Sub clients about events happening in the key space.
# This feature is documented at http://redis.io/topics/notifications
#
# For instance if keyspace events notification is enabled, and a client
# performs a DEL operation on key "foo" stored in the Database 0, two
# messages will be published via Pub/Sub:
#
# PUBLISH __keyspace@0__:foo del
# PUBLISH __keyevent@0__:del foo
#
# It is possible to select the events that Redis will notify among a set
# of classes. Every class is identified by a single character:
#
# K Keyspace events, published with __keyspace@<db>__ prefix.
# E Keyevent events, published with __keyevent@<db>__ prefix.
# g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
# $ String commands
# l List commands
# s Set commands
# h Hash commands
# z Sorted set commands
# x Expired events (events generated every time a key expires)
# e Evicted events (events generated when a key is evicted for maxmemory)
# 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
# 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:
#
# notify-keyspace-events Elg
#
# Example 2: to get the stream of the expired keys subscribing to channel
# name __keyevent@0__:expired use:
#
# notify-keyspace-events Ex
#
# By default all notifications are disabled because most users don't need
# this feature and the feature has some overhead. Note that if you don't
# specify at least one of K or E, no events will be delivered.
notify-keyspace-events ""
############################### ADVANCED CONFIG 高级配置 ###############################
# Hashes are encoded using a memory efficient data structure when they have a
# small number of entries, and the biggest entry does not exceed a given
# threshold. These thresholds can be configured using the following directives.
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
# Lists are also encoded in a special way to save a lot of space.
# The number of entries allowed per internal list node can be specified
# as a fixed maximum size or a maximum number of elements.
# For a fixed maximum size, use -5 through -1, meaning:
# -5: max size: 64 Kb <-- not recommended for normal workloads
# -4: max size: 32 Kb <-- not recommended
# -3: max size: 16 Kb <-- probably not recommended
# -2: max size: 8 Kb <-- good
# -1: max size: 4 Kb <-- good
# Positive numbers mean store up to _exactly_ that number of elements
# per list node.
# The highest performing option is usually -2 (8 Kb size) or -1 (4 Kb size),
# but if your use case is unique, adjust the settings as necessary.
list-max-ziplist-size -2
# Lists may also be compressed.
# Compress depth is the number of quicklist ziplist nodes from *each* side of
# the list to *exclude* from compression. The head and tail of the list
# are always uncompressed for fast push/pop operations. Settings are:
# 0: disable all list compression
# 1: depth 1 means "don't start compressing until after 1 node into the list,
# going from either the head or tail"
# So: [head]->node->node->...->node->[tail]
# [head], [tail] will always be uncompressed; inner nodes will compress.
# 2: [head]->[next]->node->node->...->node->[prev]->[tail]
# 2 here means: don't compress head or head->next or tail->prev or tail,
# but compress all nodes between them.
# 3: [head]->[next]->[next]->node->node->...->node->[prev]->[prev]->[tail]
# etc.
list-compress-depth 0
# Sets have a special encoding in just one case: when a set is composed
# 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.
set-max-intset-entries 512
# Similarly to hashes and lists, sorted sets are also specially encoded in
# order to save a lot of space. This encoding is only used when the length and
# elements of a sorted set are below the following limits:
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
# HyperLogLog sparse representation bytes limit. The limit includes the
# 16 bytes header. When an HyperLogLog using the sparse representation crosses
# this limit, it is converted into the dense representation.
#
# A value greater than 16000 is totally useless, since at that point the
# dense representation is more memory efficient.
#
# The suggested value is ~ 3000 in order to have the benefits of
# the space efficient encoding without slowing down too much PFADD,
# which is O(N) with the sparse encoding. The value can be raised to
# ~ 10000 when CPU is not a concern, but space is, and the data set is
# composed of many HyperLogLogs with cardinality in the 0 - 15000 range.
hll-sparse-max-bytes 3000
# Streams macro node max size / items. The stream data structure is a radix
# tree of big nodes that encode multiple items inside. Using this configuration
# it is possible to configure how big a single node can be in bytes, and the
# maximum number of items it may contain before switching to a new node when
# appending new stream entries. If any of the following settings are set to
# zero, the limit is ignored, so for instance it is possible to set just a
# max entires limit by setting max-bytes to 0 and max-entries to the desired
# value.
stream-node-max-bytes 4096
stream-node-max-entries 100
# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
# order to help rehashing the main Redis hash table (the one mapping top-level
# keys to values). The hash table implementation Redis uses (see dict.c)
# performs a lazy rehashing: the more operation you run into a hash table
# that is rehashing, the more rehashing "steps" are performed, so if the
# server is idle the rehashing is never complete and some more memory is used
# by the hash table.
#
# The default is to use this millisecond 10 times every second in order to
# actively 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 from time to time
# to queries with 2 milliseconds delay.
#
# use "activerehashing yes" if you don't have such hard requirements but
# want to free memory asap when possible.
activerehashing yes
# The client output buffer limits can be used to force disconnection of clients
# that are not reading data from the server fast enough for some reason (a
# common reason is that a Pub/Sub client can't consume messages as fast as the
# publisher can produce them).
#
# The limit can be set differently for the three different classes of clients:
#
# normal -> normal clients including MONITOR clients
# replica -> replica clients
# pubsub -> clients subscribed to at least one pubsub channel or pattern
#
# The syntax of every client-output-buffer-limit directive is the following:
#
# client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
#
# A client is immediately disconnected once the hard limit is reached, or if
# the soft limit is reached and remains reached for the specified number of
# seconds (continuously).
# So for instance if the hard limit is 32 megabytes and the soft limit is
# 16 megabytes / 10 seconds, the client will get disconnected immediately
# if the size of the output buffers reach 32 megabytes, but will also get
# disconnected if the client reaches 16 megabytes and continuously overcomes
# the limit for 10 seconds.
#
# By default normal clients are not limited because they don't receive data
# without asking (in a push way), but just after a request, so only
# asynchronous clients may create a scenario where data is requested faster
# than it can read.
#
# Instead there is a default limit for pubsub and replica clients, since
# subscribers and replicas receive data in a push fashion.
#
# Both the hard or the soft limit can be disabled by setting them to zero.
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit replica 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
# Client query buffers accumulate new commands. They are limited to a fixed
# amount by default in order to avoid that a protocol desynchronization (for
# instance due to a bug in the client) will lead to unbound memory usage in
# the query buffer. However you can configure it here if you have very special
# needs, such us huge multi/exec requests or alike.
#
# client-query-buffer-limit 1gb
# In the Redis protocol, bulk requests, that are, elements representing single
# strings, are normally limited ot 512 mb. However you can change this limit
# here.
#
# proto-max-bulk-len 512mb
# Redis calls an internal function to perform many background tasks, like
# closing connections of clients in timeout, purging expired keys that are
# never requested, and so forth.
#
# Not all tasks are performed with the same frequency, but Redis checks for
# 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
# there are many keys expiring at the same time, and timeouts may be
# handled with more precision.
#
# The range is between 1 and 500, however a value over 100 is usually not
# a good idea. Most users should use the default of 10 and raise this up to
# 100 only in environments where very low latency is required.
hz 10
# Normally it is useful to have an HZ value which is proportional to the
# number of clients connected. This is useful in order, for instance, to
# avoid too many clients are processed for each background task invocation
# in order to avoid latency spikes.
#
# Since the default HZ value by default is conservatively set to 10, Redis
# offers, and enables by default, the ability to use an adaptive HZ value
# which will temporary raise when there are many connected clients.
#
# When dynamic HZ is enabled, the actual configured HZ will be used as
# as a baseline, but multiples of the configured HZ value will be actually
# used as needed once more clients are connected. In this way an idle
# instance will use very little CPU time while a busy instance will be
# more responsive.
dynamic-hz yes
# When a child rewrites the AOF file, if the following option is enabled
# the file will be fsync-ed every 32 MB of data generated. This is useful
# in order to commit the file to the disk more incrementally and avoid
# big latency spikes.
aof-rewrite-incremental-fsync yes
# When redis saves RDB file, if the following option is enabled
# the file will be fsync-ed every 32 MB of data generated. This is useful
# in order to commit the file to the disk more incrementally and avoid
# big latency spikes.
rdb-save-incremental-fsync yes
# Redis LFU eviction (see maxmemory setting) can be tuned. However it is a good
# idea to start with the default settings and only change them after investigating
# how to improve the performances and how the keys LFU change over time, which
# is possible to inspect via the OBJECT FREQ command.
#
# There are two tunable parameters in the Redis LFU implementation: the
# counter logarithm factor and the counter decay time. It is important to
# understand what the two parameters mean before changing them.
#
# The LFU counter is just 8 bits per key, it's maximum value is 255, so Redis
# uses a probabilistic increment with logarithmic behavior. Given the value
# of the old counter, when a key is accessed, the counter is incremented in
# this way:
#
# 1. A random number R between 0 and 1 is extracted.
# 2. A probability P is calculated as 1/(old_value*lfu_log_factor+1).
# 3. The counter is incremented only if R < P.
#
# The default lfu-log-factor is 10. This is a table of how the frequency
# counter changes with a different number of accesses with different
# logarithmic factors:
#
# +--------+------------+------------+------------+------------+------------+
# | factor | 100 hits | 1000 hits | 100K hits | 1M hits | 10M hits |
# +--------+------------+------------+------------+------------+------------+
# | 0 | 104 | 255 | 255 | 255 | 255 |
# +--------+------------+------------+------------+------------+------------+
# | 1 | 18 | 49 | 255 | 255 | 255 |
# +--------+------------+------------+------------+------------+------------+
# | 10 | 10 | 18 | 142 | 255 | 255 |
# +--------+------------+------------+------------+------------+------------+
# | 100 | 8 | 11 | 49 | 143 | 255 |
# +--------+------------+------------+------------+------------+------------+
#
# NOTE: The above table was obtained by running the following commands:
#
# redis-benchmark -n 1000000 incr foo
# redis-cli object freq foo
#
# NOTE 2: The counter initial value is 5 in order to give new objects a chance
# to accumulate hits.
#
# The counter decay time is the time, in minutes, that must elapse in order
# for the key counter to be divided by two (or decremented if it has a value
# less <= 10).
#
# The default value for the lfu-decay-time is 1. A Special value of 0 means to
# decay the counter every time it happens to be scanned.
#
# lfu-log-factor 10
# lfu-decay-time 1
########################### ACTIVE DEFRAGMENTATION 碎片整理活动 #######################
#
# WARNING THIS FEATURE IS EXPERIMENTAL. However it was stress tested
# even in production and manually tested by multiple engineers for some
# time.
#
# What is active defragmentation?
# -------------------------------
#
# Active (online) defragmentation allows a Redis server to compact the
# spaces left between small allocations and deallocations of data in memory,
# thus allowing to reclaim back memory.
#
# Fragmentation is a natural process that happens with every allocator (but
# less so with Jemalloc, fortunately) and certain workloads. Normally a server
# restart is needed in order to lower the fragmentation, or at least to flush
# away all the data and create it again. However thanks to this feature
# implemented by Oran Agra for Redis 4.0 this process can happen at runtime
# in an "hot" way, while the server is running.
#
# Basically when the fragmentation is over a certain level (see the
# configuration options below) Redis will start to create new copies of the
# values in contiguous memory regions by exploiting certain specific Jemalloc
# features (in order to understand if an allocation is causing fragmentation
# and to allocate it in a better place), and at the same time, will release the
# old copies of the data. This process, repeated incrementally for all the keys
# will cause the fragmentation to drop back to normal values.
#
# Important things to understand:
#
# 1. This feature is disabled by default, and only works if you compiled Redis
# to use the copy of Jemalloc we ship with the source code of Redis.
# This is the default with Linux builds.
#
# 2. You never need to enable this feature if you don't have fragmentation
# issues.
#
# 3. Once you experience fragmentation, you can enable this feature when
# needed with the command "CONFIG SET activedefrag yes".
#
# The configuration parameters are able to fine tune the behavior of the
# defragmentation process. If you are not sure about what they mean it is
# a good idea to leave the defaults untouched.
# Enabled active defragmentation
# activedefrag yes
# Minimum amount of fragmentation waste to start active defrag
# active-defrag-ignore-bytes 100mb
# Minimum percentage of fragmentation to start active defrag
# active-defrag-threshold-lower 10
# Maximum percentage of fragmentation at which we use maximum effort
# active-defrag-threshold-upper 100
# Minimal effort for defrag in CPU percentage
# active-defrag-cycle-min 5
# Maximal effort for defrag in CPU percentage
# active-defrag-cycle-max 75
# Maximum number of set/hash/zset/list fields that will be processed from
# the main dictionary scan
# active-defrag-max-scan-fields 1000
版权声明：本文标题：Redis 配置文件详解 内容由热心网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：https://www.elefans.com/xitong/1729424462a1200768.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。
发表评论