4.      常用配置说明

####GENERAL #####################################[l1] 

 

# Bydefault Redis does not run as a daemon. Use 'yes' if you need it.

# Note that Redis will write a pid filein /var/run/redis.pid when daemonized.[l2] 

daemonize no

 

#If you run Redis from upstart or systemd, Redis can interact with your

# supervision tree. Options:[l3] 

#   supervised no      - no supervision interaction[l4] 

#   supervised upstart - signal upstartby putting Redis into SIGSTOP mode[l5] 

#   supervised systemd - signal systemdby writing READY=1 to $NOTIFY_SOCKET[l6] 

#   supervised auto    - detect upstart or systemd method based on

#                        UPSTART_JOB orNOTIFY_SOCKET environment variables[l7] 

#Note: these supervision methods only signal "process is ready."[l8] 

#       They do not enable continuous livenesspings back to your supervisor.[l9] 

supervised no

 

#If a pid file is specified, Redis writes it where specified at startup

# and removes it at exit.[l10] 

#

# Whenthe server runs non daemonized, no pid file is created if none is

# specified in the configuration. Whenthe server is daemonized, the pid file

# is used even if not specified,defaulting to "/var/run/redis.pid".[l11] 

#

#Creating a pid file is best effort: if Redis is not able to create it

# nothing bad happens, the server willstart and run normally.[l12] 

pidfile /var/run/redis_6379.pid

 

# Specifythe server verbosity level.[l13] 

# Thiscan be one of:

# debug (a lot of information, useful fordevelopment/testing)

# verbose (many rarely useful info, butnot a mess like the debug level)

# notice (moderately verbose, what youwant in production probably)

# warning (only very important / criticalmessages are logged)[l14] 

loglevel notice

 

# Specifythe 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, logswill be sent to /dev/null[l15] 

logfile ""

 

# Toenable logging to the system logger, just set 'syslog-enabled' to yes,

# and optionally update the other syslogparameters to suit your needs.

# syslog-enabled no[l16] 

 

# Specifythe syslog identity.[l17] 

# syslog-ident redis

 

# Specifythe syslog facility. Must be USER or between LOCAL0-LOCAL7.[l18] 

# syslog-facility local0

 

# Setthe number of databases. The default database is DB 0, you can select

# a different one on a per-connectionbasis using SELECT <dbid> where

# dbid is a number between 0 and'databases'-1[l19] 

databases 16

5.      快照设置说明

###### SNAPSHOTTING[l20]   ################################

#

#Save the DB on disk:[l21] 

#

#   save <seconds> <changes>[l22] 

#

#   Will save the DB if both the given numberof seconds and the given

#  number of write operations against the DB occurred.[l23] 

#

#   In the example below the behaviour will beto 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[l24] 

#

#   Note: you can disable saving completely bycommenting out all "save" lines.[l25] 

#

#   It is also possible to remove all thepreviously configured save

#  points by adding a save directive with a single empty string argument

#  like in the following example:

#

#  save ""[l26] 

 

save 900 1

save 300 10

save 60 10000

 

# Bydefault Redis will stop accepting writes if RDB snapshots are enabled

# (at least one save point) and thelatest background save failed.

# This will make the user aware (in ahard way) that data is not persisting

# on disk properly, otherwise chances arethat no one will notice and some

# disaster will happen.[l27] 

#

# Ifthe background saving process will start working again Redis will

# automatically allow writes again.[l28] 

#

# Howeverif you have setup your proper monitoring of the Redis server

# and persistence, you may want todisable this feature so that Redis will

# continue to work as usual even if thereare problems with disk,

# permissions, and so forth.[l29] 

stop-writes-on-bgsave-error yes

 

#Compress string objects using LZF when dump .rdb databases?

# For default that's set to 'yes' as it'salmost always a win.

# If you want to save some CPU in thesaving child set it to 'no' but

# the dataset will likely be bigger ifyou have compressible values or keys.[l30] 

rdbcompression yes

 

#Since version 5 of RDB a CRC64 checksum is placed at the end of the file.

# This makes the format more resistant tocorruption but there is a performance

# hit to pay (around 10%) when saving andloading RDB files, so you can disable it

# for maximum performances.[l31] 

#

#RDB files created with checksum disabled have a checksum of zero that will

# tell the loading code to skip thecheck.[l32] 

rdbchecksum yes

 

# Thefilename where to dump the DB[l33] 

dbfilename dump.rdb

 

# Theworking directory.[l34] 

#

# TheDB will be written inside this directory, with the filename specified

# above using the 'dbfilename'configuration directive.[l35] 

#

# TheAppend Only File will also be created inside this directory.[l36] 

#

# Notethat you must specify a directory here, not a file name.[l37] 

dir ./

6.      主从复制设置说明

######## REPLICATION[l38] #################################

 

# Master-Slavereplication. Use slaveof to make a Redis instance a copy of

# another Redis server. A few things tounderstand ASAP about Redis replication.[l39] 

#

# 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 slaves.[l40] 

#2) Redis slaves 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 thenext

#   sections of this file) with a sensible value depending on your needs.[l41] 

#3) Replication is automatic and does not need user intervention. After a

#   network partition slaves automatically try to reconnect to masters

#   and resynchronize with them.[l42] 

#

#slaveof <masterip> <masterport>[l43] 

 

#If the master is password protected (using the "requirepass"configuration

# directive below) it is possible to tellthe slave to authenticate before

# starting the replicationsynchronization process, otherwise the master will

# refuse the slave request.[l44] 

#

# masterauth <master-password>

 

# Whena slave loses its connection with the master, or when the replication

# is still in progress, the slave can actin two different ways:[l45] 

#

# 1)if slave-serve-stale-data is set to 'yes' (the default) the slave 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.[l46] 

#

#2) if slave-serve-stale-data is set to 'no' the slave will reply with

#   an error "SYNC with master in progress" to all the kind ofcommands

#   but to INFO and SLAVEOF.[l47] 

#

slave-serve-stale-data yes

 

# Youcan configure a slave instance to accept writes or not. Writing against

# a slave instance may be useful to storesome ephemeral data (because data

# written on a slave will be easilydeleted after resync with the master) but

# may also cause problems if clients arewriting to it because of a

# misconfiguration.[l48] 

#

#Since Redis 2.6 by default slaves are read-only[l49] .

#

# Note:read only slaves are not designed to be exposed to untrusted clients

# on the internet. It's just a protectionlayer against misuse of the instance.

# Still a read only slave exports bydefault all the administrative commands

# such as CONFIG, DEBUG, and so forth. Toa limited extent you can improve

# security of read only slaves using'rename-command' to shadow all the

# administrative / dangerous commands.[l50] 

slave-read-only yes

 

#Replication SYNC strategy: disk or socket.[l51] 

#

# -------------------------------------------------------

#WARNING: DISKLESS REPLICATION IS EXPERIMENTAL CURRENTLY[l52] 

# -------------------------------------------------------

#

# Newslaves and reconnecting slaves that are not able to continue the replication

# process just receiving differences,need to do what is called a "full

# synchronization". An RDB file istransmitted from the master to the slaves.

# The transmission can happen in twodifferent ways:[l53] 

#

# 1)Disk-backed: The Redis master creates a new process that writes the RDB

#                 file on disk. Later the fileis transferred by the parent

#                 process to the slavesincrementally.[l54] 

#2) Diskless: The Redis master creates a new process that directly writes the

#             RDB file to slave sockets,without touching the disk at all.[l55] 

#

# Withdisk-backed replication, while the RDB file is generated, more slaves

# can be queued and served with the RDBfile as soon as the current child producing

# the RDB file finishes its work. Withdiskless replication instead once

# the transfer starts, new slavesarriving will be queued and a new transfer

# will start when the current oneterminates.[l56] 

#

#When diskless replication is used, the master waits a configurable amount of

# time (in seconds) before starting thetransfer in the hope that multiple slaves

# will arrive and the transfer can beparallelized.[l57] 

#

# Withslow disks and fast (large bandwidth) networks, diskless replication

# works better.[l58] 

repl-diskless-sync no

 

# Whendiskless replication is enabled, it is possible to configure the delay

# the server waits in order to spawn thechild that transfers the RDB via socket

# to the slaves[l59] .

#

# Thisis important since once the transfer starts, it is not possible to serve

# new slaves arriving, that will bequeued for the next RDB transfer, so the server

# waits a delay in order to let moreslaves arrive.[l60] 

#

# Thedelay is specified in seconds, and by default is 5 seconds. To disable

# it entirely just set it to 0 secondsand the transfer will start ASAP.[l61] 

repl-diskless-sync-delay 5

 

# Slavessend PINGs to server in a predefined interval. It's possible to change

# this interval with the repl_ping_slave_periodoption. The default value is 10

# seconds.[l62] 

#

# repl-ping-slave-period 10

 

# Thefollowing option sets the replication timeout for:[l63] 

#

# 1)Bulk transfer I/O during SYNC, from the point of view of slave.

# 2) Master timeout from the point ofview of slaves (data, pings).

# 3) Slave timeout from the point of viewof masters (REPLCONF ACK pings).[l64] 

#

#It is important to make sure that this value is greater than the value

# specified for repl-ping-slave-periodotherwise a timeout will be detected

# every time there is low traffic betweenthe master and the slave.[l65] 

#

# repl-timeout 60

 

# DisableTCP_NODELAY on the slave socket after SYNC?[l66] 

#

#If you select "yes" Redis will use a smaller number of TCP packetsand

# less bandwidth to send data to slaves.But this can add a delay for

# the data to appear on the slave side,up to 40 milliseconds with

# Linux kernels using a defaultconfiguration.[l67] 

#

# Ifyou select "no" the delay for data to appear on the slave side will

# be reduced but more bandwidth will beused for replication.[l68] 

#

#By default we optimize for low latency, but in very high traffic conditions

# or when the master and slaves are manyhops away, turning this to "yes" may

# be a good idea.[l69] 

repl-disable-tcp-nodelay no

 

#Set the replication backlog size. The backlog is a buffer that accumulates

# slave data when slaves are disconnectedfor some time, so that when a slave

# wants to reconnect again, often a fullresync is not needed, but a partial

# resync is enough, just passing theportion of data the slave missed while

# disconnected.[l70] 

#

# Thebigger the replication backlog, the longer the time the slave can be

# disconnected and later be able toperform a partial resynchronization.[l71] 

#

#The backlog is only allocated once there is at least a slave connected[l72] .

#

# repl-backlog-size 1mb

 

# Aftera master has no longer connected slaves for some time, the backlog

# will be freed. The following optionconfigures the amount of seconds that

# need to elapse, starting from the timethe last slave disconnected, for

# the backlog buffer to be freed.[l73] 

#

# Avalue of 0 means to never release the backlog.[l74] 

#

# repl-backlog-ttl 3600

 

# Theslave priority is an integer number published by Redis in the INFO output.

# It is used by Redis Sentinel in orderto select a slave to promote into a

# master if the master is no longerworking correctly.[l75] 

#

# Aslave with a low priority number is considered better for promotion, so

# for instance if there are three slaveswith priority 10, 100, 25 Sentinel will

# pick the one with priority 10, that isthe lowest.[l76] 

#

# Howevera special priority of 0 marks the slave as not able to perform the

# role of master, so a slave withpriority of 0 will never be selected by

# Redis Sentinel for promotion.[l77] 

#

#By default the priority is 100.[l78] 

slave-priority 100

 

# Itis possible for a master to stop accepting writes if there are less than

# N slaves connected, having a lag lessor equal than M seconds.[l79] 

#

# TheN slaves need to be in "online" state.[l80] 

#

# Thelag in seconds, that must be <= the specified value, is calculated from

# the last ping received from the slave,that is usually sent every second.[l81] 

#

#This option does not GUARANTEE that N replicas will accept the write, but

# will limit the window of exposure forlost writes in case not enough slaves

# are available, to the specified numberof seconds.[l82] 

#

# Forexample to require at least 3 slaves with a lag <= 10 seconds use:[l83] 

#

# min-slaves-to-write 3

# min-slaves-max-lag 10

#

# Settingone or the other to 0 disables the feature.[l84] 

#

#By default min-slaves-to-write is set to 0 (feature disabled) and

# min-slaves-max-lag is set to 10.[l85] 

 

# ARedis master is able to list the address and port of the attached

# slaves in different ways. For examplethe "INFO replication" section

# offers this information, which is used,among other tools, by

# Redis Sentinel in order to discoverslave instances.

# Another place where this info isavailable is in the output of the

# "ROLE" command of a masteer.[l86] 

#

#The listed IP and address normally reported by a slave is obtained

# in the following way:[l87] 

#

#   IP:The address is auto detected by checking the peer address

#  of the socket used by the slave to connect with the master.[l88] 

#

#   Port: The port is communicated by theslave during the replication

#  handshake, and is normally the port that the slave is using to

#  list for connections.[l89] 

#

#However when port forwarding or Network Address Translation (NAT) is

# used, the slave may be actuallyreachable via different IP and port

# pairs. The following two options can beused by a slave in order to

# report to its master a specific set ofIP and port, so that both INFO

# and ROLE will report those values.[l90] 

#

# Thereis no need to use both the options if you need to override just

# the port or the IP address.[l91] 

#

# slave-announce-ip 5.5.5.5

# slave-announce-port 1234

 [l1]常用配置说明

 [l2]默认情况下Redis不作为守护程序运行。 如果需要，使用“yes”。 注意，Redis在守护进程时会在/var/run/redis.pid中写一个pid文件。

 [l3]如果从upstart或systemd运行Redis，Redis可以与您的管理树进行交互。选项：

 [l4]无管理的互动

 [l5]通过将Redis置于SIGSTOP模式来使信号Upstart

 [l6]通过将READY = 1写入$ NOTIFY_SOCKET信号systemd

 [l7]基于UPSTART_JOB或NOTIFY_SOCKET环境变量检测upstart或systemd方法

 [l8]注意：这些管理方法只是信号“过程就绪”。

 [l9]他们不能连续的liveness ping回你的管理。

 [l10]如果指定了pid文件，Redis会启动时在指定的位置写入该文件，并在退出时将其删除。

 [l11]当服务器运行非守护进程时，如果在配置中未指定任何pid文件，则不会创建pid文件。当服务器进行守护进程时，即使未指定，也使用pid文件，默认为“/var/run/redis.pid”。

 [l12]创建pid文件是最好的努力：如果Redis无法创建它没有什么不好发生，服务器将启动并正常运行。

 [l13]定义日志级别

 [l14]这可以是以下之一：

debug（很多信息，对开发/测试有用）
verbose（很少有用的信息，但不像调试级别的混乱）
notice（适度冗长，适用于生成环境）

warning（仅记录非常重要/关键的消息）

 [l15]指定日志文件名。 此外，空字符串可用于强制Redis登录标准输出。 请注意，如果您使用标准输出进行日志记录，但使用守护进程，则日志将发送到/ dev / null

 [l16]要启用日志记录到系统记录器，只需将“syslog-enabled”设置为yes，并可选择更新其他syslog参数以满足您的需要。 syslog启用no

 [l17]指定syslog标识。

 [l18]指定syslog设施。 必须是USER或LOCAL0-LOCAL7之间。

 [l19]设置数据库的数量。 默认数据库是DB 0，可以使用SELECT<dbid>在每个连接的基础上选择不同的数据库，其中dbid是介于0和'databases'-1之间的数字

 [l20]快照

 [l21]将数据存入硬盘

 [l22]格式：save <间隔时间（秒）> <写入次数>

 [l23]根据给定的时间间隔和写入次数将数据保存到磁盘

 [l24]下面的例子的意思是：
900 秒内如果至少有 1 个 key 的值变化，则保存
300 秒内如果至少有 10 个 key 的值变化，则保存
60 秒内如果至少有 10000 个 key 的值变化，则保存

 [l25]注意：你可以注释掉所有的save行来停用保存功能。

 [l26]也可以通过添加具有单个空字符串参数的save指令来删除所有以前配置的保存点，如下例所示：save "" [l26]

 [l27]默认情况下，如果启用了RDB快照（至少一个保存点）并且最近的后台保存失败，Redis将停止接受写入。这将使用户意识到（以硬的方式）数据不是正确地持久存储在磁盘上，否则可能是没有人会注意到灾难的发生。

 [l28]如果后台报错进程重新启动了，redis也将自动的允许写操作

 [l29]但是，如果你有设置您的Redis的服务器和持久性的适当监督，你可能要禁用此功能，Redis的将继续照常即使有磁盘，权限问题的工作，等等。

 [l30]转储.rdb数据库时使用LZF压缩字符串对象？ 对于被设置为“是”。如果你想节省一些CPU在节能孩子将其设置为“无”，但该数据集可能会更大，如果你有可压缩数值或按键。

 [l31]从RDB的版本5开始，在文件的末尾会进行CRC64校验。 这使得格式更加严谨，但是在保存和加载RDB文件时有一个性能损失（大约10％），所以你可以禁用它的最大性能。

 [l32]禁用和创建的RDB文件的校验，这将告诉加载代码跳过检查

 [l33]转储数据库的文件名

 [l34]工作目录

 [l35]DB将使用'dbfilename'配置指令在此目录中写入上面指定的文件名。

 [l36]追加文件也将在此目录中创建。

 [l37]请注意，您必须在此指定目录，而不是文件名。

 [l38]主从复制

 [l39]主从复制。 使用slaveof使Redis实例成为另一个Redis服务器的副本。 关于Redis复制的几个事情。

 [l40]1）Redis复制是异步的，但是如果它看起来没有与指定的从设备连接，您可以将主机配置为停止接受写入。

 [l41]2）如果复制链路丢失相对较少的时间，Redis从设备能够与主设备执行部分重新同步。您可能需要根据您的需要使用合理的值配置复制积压大小（请参阅此文件的下一部分）。

 [l42]3）复制是自动的，不需要用户干预。 网络分区后，自动尝试重新连接到主控器并与它们重新同

 [l43]注意这个只需要在slave上配置，

配置格式是：slaveof 主IP  主端口

 [l44]如果主密码保护（使用下面的“requirepass”配置指令），可以在开始复制同步过程之前告诉从设备进行认证，否则主设备将拒绝从设备请求。

 [l45]当从站失去与主站的连接时，或者当复制仍在进行中时，从站可能有两种表现：

 [l46]1）如果slave-serve-stale-data设置为“yes”（默认值），则从设备仍将回复客户端请求，可能使用过期数据，或者如果这是第一个同步，则数据集可能只为空

 [l47]2）如果slave-serve-stale-data设置为“no”，从设备将回复错误“SYNC with master in progress”给除INFO和SLAVEOF意外所有类型的命令。

 [l48]您可以配置从实例接受写入或不接受写入。对从实例进行写操作对于存储一些临时数据可能是有用的（因为写在从属设备上的数据将在与主设备重新同步后很容易被删除），但是如果客户端因为错误配置而写入它，也会导致问题

 [l49]从Redis 2.6默认的从机是只读的

 [l50]注意：只读从站不设计为暴露给互联网上的不受信任的客户端。 它只是一个防止实例滥用的保护层。只读slave默认情况下输出所有管理命令，如CONFIG，DEBUG等等。在有限的程度上，您可以使用“rename-command”来提高只读从设备的安全性，以隐藏所有管理/危险命令

 [l51]复制SYNC策略：磁盘或套接字。

 [l52]警告：不可靠的复制是当前的设置

 [l53]新的从和重新连接的从，不能继续复制过程只是接收差异，需要做的就是所谓的“完全同步”。 RDB文件从主机传输到从机。传输可以以两种不同的方式：

 [l54]1）磁盘支持：Redis主机创建一个新的进程，将RDB文件写入磁盘。稍后，文件由父进程以增量方式传送到从属。

 [l55]2）无盘：Redis主机创建一个新的进程，直接将RDB文件写入从属插槽，而不触及磁盘。

 [l56]使用磁盘支持的复制，在生成RDB文件时，只要生成RDB文件的当前子项完成其工作，就可以排队更多的从属并使用RDB文件提供。使用无盘复制，一旦传输开始，新从站到达将排队，并且当当前终止时新的传输将开始

 [l57]当使用无盘复制时，主机在开始传输之前等待可配置的时间量（以秒为单位），以防止多个从机到达并且传输可以并行化。

 [l58]使用慢磁盘和快速（大带宽）网络，无盘复制的效果更好。

 [l59]当启用无盘复制时，可以配置服务器等待的延迟，以便生成通过套接字将RDB传输到从属的子节点

 [l60]这是很重要的，因为一旦传输开始，不可能服务新的从设备到达，将为下一个RDB传输排队，因此服务器等待延迟，以便让更多的从设备到达。

 [l61]延迟以秒为单位指定，默认值为5秒。 要完全禁用它只是设置为0秒，传输将尽快启动

 [l62]从设备以预定义的时间间隔向服务器发送PING。可以使用repl_ping_slave_period选项更改此时间间隔。默认值为10秒

 [l63]以下选项设置复制超时：

 [l64]1）SYNC期间的批量传输I / O，从从机的角度看。
2）从从机（数据，ping）的角度看主机超时。
3）从主机（REPLCONF ACK ping）的角度看从机超时

 [l65]重要的是要确保此值大于为repl-ping-slave-period指定的值，否则每次主站和从站之间的流量低时都会检测到超时。

 [l66]SYNC之后在从站插槽上禁用TCP_NODELAY？

 [l67]如果选择“是”，Redis将使用较少数量的TCP数据包和较少的带宽将数据发送到从站。 但是这可以增加数据在从端面上出现的延迟，对于Linux内核，使用默认配置可以延迟40毫秒

 [l68]如果选择“否”，数据在从机端显示的延迟将会减少，但更多的带宽将用于复制。

 [l69]默认情况下，我们针对低延迟进行优化，但在非常高的流量条件下或当主设备和从设备有许多跳时，将其转换为“是”可能是一个好主意。

 [l70]设置复制容量大小。 容量是一个缓冲器，当从机断开一段时间时积累从机数据，以便当从机想要再次重新连接时，通常不需要完全再同步，但是部分再同步就足够了，只是将在断开连接时的数据传递给从机

 [l71]复制容量越大，从设备可以断开连接的时间就越长，以后就可以执行部分重新同步。

 [l72]只有至少有一个从站连接时才分配容量大小

 [l73]在主机已经不再连接从机一段时间后，容纳将被释放。 以下选项配置从最后一个从服务器断开的时间开始，需要经过的秒数，以使待处理缓冲区被释放

 [l74]值为0表示永不释放backlog。

 [l75]从属优先级是由Redis在INFO输出中发布的整数。 它由RedisSentinel使用，以便选择从属设备，如果主设备不再正常工作，则升级为主设备

 [l76]具有低优先级编号的从设备被认为更好的提升，因此如果存在具有优先级10,100,25的三个从设备，则哨兵将选择具有优先级10，即最低的那个。

 [l77]然而，0的特殊优先级标志着从设备不能执行主设备的角色，因此优先级为0的从设备将不会被Redis Sentinel选择用于升级。

 [l78]默认优先级为100

 [l79]如果存在少于连接的从设备，具有小于或等于M秒的滞后，则主设备可以停止接受写入。

 [l80]N个从站需要处于“在线”状态。

 [l81]以秒为单位的滞后，必须小于指定值，根据从从设备接收的最后一次ping计算，通常每秒发送一次。

 [l82]此选项不保证N个副本将接受写入，但会在没有足够从属设备可用的情况下将丢失写入的曝光窗口限制为指定的秒数。

 [l83]例如，要求至少3个滞后<= 10秒的从站使用：

 [l84]将一个或另一个设置为0将禁用该功能。

 [l85]默认情况下，min-slave-to-write设置为0（禁用功能），min-slaves-max-lag设置为10。

 [l86]Redis主机能够以不同的方式列出所连接从机的地址和端口。例如，“INFO复制”部分提供此信息，除了其他工具之外，Redis Sentinel还使用该信息来发现从属实例。此信息可用的另一个地方是在masterser的“ROLE”命令的输出中

 [l87]通过从设备正常报告的列出的IP和地址通过以下方式获得：

 [l88]IP：通过检查从设备与主设备连接使用的套接字的对等体地址自动检测地址。

 [l89]端口：端口在复制握手期间由从设备通信，并且通常是从设备正用于列出连接的端口。

 [l90]然而，当使用端口转发或网络地址转换（NAT）时，从属实际上可以通过不同的IP和端口对来到达。以下两个选项可以由从设备使用，以便向其主设备报告一组特定的IP和端口，以便INFO和ROLE将报告这些值

 [l91]如果您需要仅覆盖端口或IP地址，则不需要使用这两个选项。