Docker部署容器

Docker部署容器

Docker 常用命令
Docker 安装

配置文件必须在运行容器前完成创建和配置，否则无法使其生效

1.1.1部署 nginx

1.简易安装

docker run -d \
  --restart=always \
  --name nginx \
  -p 80:80 \
  nginx:1.24

1. docker run: 基于指定的镜像创建一个新的容器并运行它。
2. d: 这是“detached mode”的缩写，意味着容器将在后台运行，并返回容器的ID。你不会直接看到容器的输出，除非使用docker logs命令查看日志或者使用docker attach命令连接到容器。
3. -restart=always: 这是一个重启策略，表示无论容器的退出状态如何，Docker都应该始终尝试重启这个容器。这特别有用在生产环境中，以确保即使服务遇到临时问题也能自动恢复。
4. -name nginx: 为新创建的容器指定一个名称，这里是nginx。通过给容器命名，你可以更容易地通过名称来引用和管理它，而不是使用容器的ID。
5. p 80:80: 端口映射。这表示将宿主机的80端口映射到容器的80端口。这样，当你访问宿主机的80端口时，请求实际上会被转发到容器的80端口。
6. nginx:1.24: 这是你想要基于的Docker镜像的名称和标签。在这里，你选择了nginx镜像的1.24版本。Docker会从它的镜像仓库（通常是Docker Hub）中拉取这个版本的镜像，并基于这个镜像创建和运行容器。

2.挂载数据卷安装（html：文件夹，nginx.conf：文件）

提前创建对应文件夹

mkdir -p /usr/local/docker_data/nginx/html
mkdir -p /usr/local/docker_data/nginx/conf
mkdir -p /usr/local/docker_data/nginx/logs

在 nginx 里创建 nginx.conf 文件（必须在创建运行nginx容器前完成）

vim /usr/local/docker_data/nginx/conf/nginx.conf

在nginx.conf文件中加入以下内容

#user  nobody;#运行nginx的默认账号
#nginx进程数，建议设置为等于CPU总核心数。
worker_processes  1;
 
#事件区块开始
events {
    #单个进程最大链接数（最大连接数=连接数*进程数）
    #根据硬件调整，与前面工作进程配合起来用，尽量大，但别把CPU跑到100%就行，每个进程允许的最多连接数，理论上为每台nginx服务器的最大连接数
    worker_connections  1024;
}
 
#设定http服务器，利用它的反向代理功能提供负载均衡支持
http {
    #include:导入外部文件mime.types,将所有types提取为文件，然后导入到nginx配置文件中。
    include       mime.types;
    #默认文件类型
    default_type  application/octet-stream;
    
    #开启高效文件传输模式，sendfile指令指定nginx是否调用sendfile函数来输出文件，对于普通应用设置为on，如果用来进行下载等应用磁盘IO重负载应用，可设置为off，以平衡磁盘与网络I/O处理速度，降低系统的负载，注意：如果图片显示不正常把这个改成off
    #sendfile指令指定，nginx是否调用sendfile函数（zero copy方式）来输出文件，对于普通应用，必须设为on,如果用来进行下载等应用磁盘IO重负载应用，可设置为off，以平衡磁盘与网络IO处理速度，降低系统uptime
    sendfile        on;
    #长连接超时事件，单位是秒
    keepalive_timeout  65;
 
  
    #第一个server区块开始，表示一个独立的虚拟主机站点
    server {
        #提供服务的端口，默认80
        listen       80;
        #提供服务的域名主机名
        server_name  localhost;
 
        
        #对 “/” 启动反向代理，第一个location区块开始
        location / {
            root   html;    #服务默认启动目录,可以改成指定的目录位置
            index  index.html index.htm; #默认的首页文件，多个用空格分开
        }
 
        #错误页面路由
        error_page   500 502 503 504  /50x.html; # 出现对应的http状态码是，使用50x.html回应客户
        location = /50x.html { # location区块开始，访问50x.html
            root   html; # 指定对应的站点目录为html
        }
 
    }
 
 
}

创建并运行新nginx容器，挂载本地目录

docker run -d \
  --restart=always \
  --name nginx \
  -p 80:80 \
  -v /usr/local/docker_data/nginx/html:/usr/share/nginx/html \
  -v /usr/local/docker_data/nginx/conf/nginx.conf:/etc/nginx/nginx.conf \
  -v /usr/local/docker_data/nginx/logs:/var/log/nginx \
  nginx:1.24
	

3.设置Nginx开机启动（略）

vim /etc/rc.local

文本底部追加（如果有则不用修改）

/usr/local/nginx/sbin/nginx

4.查看Nginx进程是否启动

ps -ef|grep nginx

1.1.2部署 redis

1.简易安装

docker run -d \
	--restart=always \
	--name redis \
	--requirepass pwd123456\
	-p 6379:6379 \
	redis:7.0.12  

2.挂载数据卷安装

提前创建对应文件夹

mkdir -p /usr/local/docker_data/redis/conf
mkdir -p /usr/local/docker_data/redis/data

在 /usr/local/docker_data/redis/conf 文件夹内创建一个redis.conf文件

vim /usr/local/docker_data/redis/conf/redis.conf

写入自定义配置

• redis.conf配置

  # Redis configuration file example.
  #
  # Note that in order to read the configuration file, Redis must be
  # started with the file path as first argument:
  #
  # ./redis-server /path/to/redis.conf
  
  # Note on units: when memory size is needed, it is possible to specify
  # it in the usual form of 1k 5GB 4M and so forth:
  #
  # 1k => 1000 bytes
  # 1kb => 1024 bytes
  # 1m => 1000000 bytes
  # 1mb => 1024*1024 bytes
  # 1g => 1000000000 bytes
  # 1gb => 1024*1024*1024 bytes
  #
  # units are case insensitive so 1GB 1Gb 1gB are all the same.
  
  ################################## INCLUDES ###################################
  
  # Include one or more other config files here.  This is useful if you
  # have a standard template that goes to all Redis servers but also need
  # to customize a few per-server settings.  Include files can include
  # other files, so use this wisely.
  #
  # Note that option "include" won't be rewritten by command "CONFIG REWRITE"
  # from admin or Redis Sentinel. Since Redis always uses the last processed
  # line as value of a configuration directive, you'd better put includes
  # at the beginning of this file to avoid overwriting config change at runtime.
  #
  # If instead you are interested in using includes to override configuration
  # options, it is better to use include as the last line.
  #
  # include /path/to/local.conf
  # include /path/to/other.conf
  
  ################################## 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 /path/to/my_module.so
  # loadmodule /path/to/other_module.so
  
  ################################## NETWORK #####################################
  
  # By default, if no "bind" configuration directive is specified, Redis listens
  # for connections from all available network interfaces on the host machine.
  # It is possible to listen to just one or multiple selected interfaces using
  # the "bind" configuration directive, followed by one or more IP addresses.
  # Each address can be prefixed by "-", which means that redis will not fail to
  # start if the address is not available. Being not available only refers to
  # addresses that does not correspond to any network interfece. Addresses that
  # are already in use will always fail, and unsupported protocols will always BE
  # silently skipped.
  #
  # Examples:
  #
  # bind 192.168.1.100 10.0.0.1     # listens on two specific IPv4 addresses
  # bind 127.0.0.1 ::1              # listens on loopback IPv4 and IPv6
  # bind * -::*                     # like the default, all available interfaces
  #
  # ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the
  # internet, binding to all the interfaces is dangerous and will expose the
  # instance to everybody on the internet. So by default we uncomment the
  # following bind directive, that will force Redis to listen only on the
  # IPv4 and IPv6 (if available) loopback interface addresses (this means Redis
  # will only be able to accept client connections from the same host that it is
  # running on).
  #
  # IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES
  # JUST COMMENT OUT THE FOLLOWING LINE.
  # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  #bind 127.0.0.1 -::1
  bind 0.0.0.0
  
  # Protected mode is a layer of security protection, in order to avoid that
  # Redis instances left open on the internet are accessed and exploited.
  #
  # When protected mode is on and if:
  #
  # 1) The server is not binding explicitly to a set of addresses using the
  #    "bind" directive.
  # 2) No password is configured.
  #
  # The server only accepts connections from clients connecting from the
  # IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain
  # sockets.
  #
  # By default protected mode is enabled. You should disable it only if
  # you are sure you want clients from other hosts to connect to Redis
  # even if no authentication is configured, nor a specific set of interfaces
  # are explicitly listed using the "bind" directive.
  protected-mode yes
  
  # Accept connections on the specified port, default is 6379 (IANA #815344).
  # If port 0 is specified Redis will not listen on a TCP socket.
  port 6379
  
  # TCP listen() backlog.
  #
  # In high requests-per-second environments you need a high backlog in order
  # to avoid slow clients connection issues. Note that the Linux kernel
  # will silently truncate it to the value of /proc/sys/net/core/somaxconn so
  # make sure to raise both the value of somaxconn and tcp_max_syn_backlog
  # in order to get the desired effect.
  tcp-backlog 511
  
  # Unix socket.
  #
  # Specify the path for the Unix socket that will be used to listen for
  # incoming connections. There is no default, so Redis will not listen
  # on a unix socket when not specified.
  #
  # unixsocket /run/redis.sock
  # unixsocketperm 700
  
  # Close the connection after a client is idle for N seconds (0 to disable)
  timeout 0
  
  # TCP keepalive.
  #
  # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
  # of communication. This is useful for two reasons:
  #
  # 1) Detect dead peers.
  # 2) Force network equipment in the middle to consider the connection to be
  #    alive.
  #
  # On Linux, the specified value (in seconds) is the period used to send ACKs.
  # Note that to close the connection the double of the time is needed.
  # On other kernels the period depends on the kernel configuration.
  #
  # A reasonable value for this option is 300 seconds, which is the new
  # Redis default starting with Redis 3.2.1.
  tcp-keepalive 300
  
  ################################# TLS/SSL #####################################
  
  # By default, TLS/SSL is disabled. To enable it, the "tls-port" configuration
  # directive can be used to define TLS-listening ports. To enable TLS on the
  # default port, use:
  #
  # port 0
  # tls-port 6379
  
  # Configure a X.509 certificate and private key to use for authenticating the
  # server to connected clients, masters or cluster peers.  These files should be
  # PEM formatted.
  #
  # tls-cert-file redis.crt 
  # tls-key-file redis.key
  #
  # If the key file is encrypted using a passphrase, it can be included here
  # as well.
  #
  # tls-key-file-pass secret
  
  # Normally Redis uses the same certificate for both server functions (accepting
  # connections) and client functions (replicating from a master, establishing
  # cluster bus connections, etc.).
  #
  # Sometimes certificates are issued with attributes that designate them as
  # client-only or server-only certificates. In that case it may be desired to use
  # different certificates for incoming (server) and outgoing (client)
  # connections. To do that, use the following directives:
  #
  # tls-client-cert-file client.crt
  # tls-client-key-file client.key
  #
  # If the key file is encrypted using a passphrase, it can be included here
  # as well.
  #
  # tls-client-key-file-pass secret
  
  # Configure a DH parameters file to enable Diffie-Hellman (DH) key exchange:
  #
  # tls-dh-params-file redis.dh
  
  # Configure a CA certificate(s) bundle or directory to authenticate TLS/SSL
  # clients and peers.  Redis requires an explicit configuration of at least one
  # of these, and will not implicitly use the system wide configuration.
  #
  # tls-ca-cert-file ca.crt
  # tls-ca-cert-dir /etc/ssl/certs
  
  # By default, clients (including replica servers) on a TLS port are required
  # to authenticate using valid client side certificates.
  #
  # If "no" is specified, client certificates are not required and not accepted.
  # If "optional" is specified, client certificates are accepted and must be
  # valid if provided, but are not required.
  #
  # tls-auth-clients no
  # tls-auth-clients optional
  
  # By default, a Redis replica does not attempt to establish a TLS connection
  # with its master.
  #
  # Use the following directive to enable TLS on replication links.
  #
  # tls-replication yes
  
  # By default, the Redis Cluster bus uses a plain TCP connection. To enable
  # TLS for the bus protocol, use the following directive:
  #
  # tls-cluster yes
  
  # By default, only TLSv1.2 and TLSv1.3 are enabled and it is highly recommended
  # that older formally deprecated versions are kept disabled to reduce the attack surface.
  # You can explicitly specify TLS versions to support.
  # Allowed values are case insensitive and include "TLSv1", "TLSv1.1", "TLSv1.2",
  # "TLSv1.3" (OpenSSL >= 1.1.1) or any combination.
  # To enable only TLSv1.2 and TLSv1.3, use:
  #
  # tls-protocols "TLSv1.2 TLSv1.3"
  
  # Configure allowed ciphers.  See the ciphers(1ssl) manpage for more information
  # about the syntax of this string.
  #
  # Note: this configuration applies only to <= TLSv1.2.
  #
  # tls-ciphers DEFAULT:!MEDIUM
  
  # Configure allowed TLSv1.3 ciphersuites.  See the ciphers(1ssl) manpage for more
  # information about the syntax of this string, and specifically for TLSv1.3
  # ciphersuites.
  #
  # tls-ciphersuites TLS_CHACHA20_POLY1305_SHA256
  
  # When choosing a cipher, use the server's preference instead of the client
  # preference. By default, the server follows the client's preference.
  #
  # tls-prefer-server-ciphers yes
  
  # By default, TLS session caching is enabled to allow faster and less expensive
  # reconnections by clients that support it. Use the following directive to disable
  # caching.
  #
  # tls-session-caching no
  
  # Change the default number of TLS sessions cached. A zero value sets the cache
  # to unlimited size. The default size is 20480.
  #
  # tls-session-cache-size 5000
  
  # Change the default timeout of cached TLS sessions. The default timeout is 300
  # seconds.
  #
  # tls-session-cache-timeout 60
  
  ################################# GENERAL #####################################
  
  # By default Redis does not run as a daemon. Use 'yes' if you need it.
  # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
  # When Redis is supervised by upstart or systemd, this parameter has no impact.
  daemonize yes
  
  # If you run Redis from upstart or systemd, Redis can interact with your
  # supervision tree. Options:
  #   supervised no      - no supervision interaction
  #   supervised upstart - signal upstart by putting Redis into SIGSTOP mode
  #                        requires "expect stop" in your upstart job config
  #   supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET
  #                        on startup, and updating Redis status on a regular
  #                        basis.
  #   supervised auto    - detect upstart or systemd method based on
  #                        UPSTART_JOB or NOTIFY_SOCKET environment variables
  # Note: these supervision methods only signal "process is ready."
  #       They do not enable continuous pings back to your supervisor.
  #
  # The default is "no". To run under upstart/systemd, you can simply uncomment
  # the line below:
  #
  # supervised auto
  
  # If a pid file is specified, Redis writes it where specified at startup
  # and removes it at exit.
  #
  # When the server runs non daemonized, no pid file is created if none is
  # specified in the configuration. When the server is daemonized, the pid file
  # is used even if not specified, defaulting to "/var/run/redis.pid".
  #
  # Creating a pid file is best effort: if Redis is not able to create it
  # nothing bad happens, the server will start and run normally.
  #
  # Note that on modern Linux systems "/run/redis.pid" is more conforming
  # and should be used instead.
  pidfile /var/run/redis_6379.pid
  
  # Specify the server verbosity level.
  # This can be one of:
  # debug (a lot of information, useful for development/testing)
  # verbose (many rarely useful info, but not a mess like the debug level)
  # notice (moderately verbose, what you want in production probably)
  # warning (only very important / critical messages are logged)
  loglevel notice
  
  # Specify the log file name. Also the empty string can be used to force
  # Redis to log on the standard output. Note that if you use standard
  # output for logging but daemonize, logs will be sent to /dev/null
  logfile "redis.log"
  
  # To enable logging to the system logger, just set 'syslog-enabled' to yes,
  # and optionally update the other syslog parameters to suit your needs.
  # syslog-enabled no
  
  # Specify the syslog identity.
  # syslog-ident redis
  
  # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
  # syslog-facility local0
  
  # To disable the built in crash log, which will possibly produce cleaner core
  # dumps when they are needed, uncomment the following:
  #
  # crash-log-enabled no
  
  # To disable the fast memory check that's run as part of the crash log, which
  # will possibly let redis terminate sooner, uncomment the following:
  #
  # crash-memcheck-enabled no
  
  # Set the number of databases. The default database is DB 0, you can select
  # a different one on a per-connection basis using SELECT <dbid> where
  # dbid is a number between 0 and 'databases'-1
  databases 16
  
  # 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 and syslog logging is
  # disabled. 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 no
  
  # By default, Redis modifies the process title (as seen in 'top' and 'ps') to
  # provide some runtime information. It is possible to disable this and leave
  # the process name as executed by setting the following to no.
  set-proc-title yes
  
  # When changing the process title, Redis uses the following template to construct
  # the modified title.
  #
  # Template variables are specified in curly brackets. The following variables are
  # supported:
  #
  # {title}           Name of process as executed if parent, or type of child process.
  # {listen-addr}     Bind address or '*' followed by TCP or TLS port listening on, or
  #                   Unix socket if only that's available.
  # {server-mode}     Special mode, i.e. "[sentinel]" or "[cluster]".
  # {port}            TCP port listening on, or 0.
  # {tls-port}        TLS port listening on, or 0.
  # {unixsocket}      Unix domain socket listening on, or "".
  # {config-file}     Name of configuration file used.
  #
  proc-title-template "{title} {listen-addr} {server-mode}"
  
  ################################ SNAPSHOTTING  ################################
  
  # Save the DB to disk.
  #
  # save <seconds> <changes>
  #
  # Redis will save the DB if both the given number of seconds and the given
  # number of write operations against the DB occurred.
  #
  # Snapshotting can be completely disabled with a single empty string argument
  # as in following example:
  #
  # save ""
  #
  # Unless specified otherwise, by default Redis will save the DB:
  #   * After 3600 seconds (an hour) if at least 1 key changed
  #   * After 300 seconds (5 minutes) if at least 100 keys changed
  #   * After 60 seconds if at least 10000 keys changed
  #
  # You can set these explicitly by uncommenting the three following lines.
  #
  # save 3600 1
  # save 300 100
  # save 60 10000
  
  # By default Redis will stop accepting writes if RDB snapshots are enabled
  # (at least one save point) and the latest background save failed.
  # This will make the user aware (in a hard way) that data is not persisting
  # on disk properly, otherwise chances are that no one will notice and some
  # disaster will happen.
  #
  # If the background saving process will start working again Redis will
  # automatically allow writes again.
  #
  # However if you have setup your proper monitoring of the Redis server
  # and persistence, you may want to disable this feature so that Redis will
  # continue to work as usual even if there are problems with disk,
  # permissions, and so forth.
  stop-writes-on-bgsave-error yes
  
  # Compress string objects using LZF when dump .rdb databases?
  # By default compression is enabled as it's almost always a win.
  # If you want to save some CPU in the saving child set it to 'no' but
  # the dataset will likely be bigger if you have compressible values or keys.
  rdbcompression yes
  
  # Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
  # This makes the format more resistant to corruption but there is a performance
  # hit to pay (around 10%) when saving and loading RDB files, so you can disable it
  # for maximum performances.
  #
  # RDB files created with checksum disabled have a checksum of zero that will
  # tell the loading code to skip the check.
  rdbchecksum yes
  
  # Enables or disables full sanitation checks for ziplist and listpack etc when
  # loading an RDB or RESTORE payload. This reduces the chances of a assertion or
  # crash later on while processing commands.
  # Options:
  #   no         - Never perform full sanitation
  #   yes        - Always perform full sanitation
  #   clients    - Perform full sanitation only for user connections.
  #                Excludes: RDB files, RESTORE commands received from the master
  #                connection, and client connections which have the
  #                skip-sanitize-payload ACL flag.
  # The default should be 'clients' but since it currently affects cluster
  # resharding via MIGRATE, it is temporarily set to 'no' by default.
  #
  # sanitize-dump-payload no
  
  # The filename where to dump the DB
  dbfilename dump.rdb
  
  # Remove RDB files used by replication in instances without persistence
  # enabled. By default this option is disabled, however there are environments
  # where for regulations or other security concerns, RDB files persisted on
  # disk by masters in order to feed replicas, or stored on disk by replicas
  # in order to load them for the initial synchronization, should be deleted
  # ASAP. Note that this option ONLY WORKS in instances that have both AOF
  # and RDB persistence disabled, otherwise is completely ignored.
  #
  # An alternative (and sometimes better) way to obtain the same effect is
  # to use diskless replication on both master and replicas instances. However
  # in the case of replicas, diskless is not always an option.
  rdb-del-sync-files no
  
  # The working directory.
  #
  # The DB will be written inside this directory, with the filename specified
  # above using the 'dbfilename' configuration directive.
  #
  # The Append Only File will also be created inside this directory.
  #
  # Note that you must specify a directory here, not a file name.
  # 工作目录，默认是当前目录，也就是运行redis-server时的命令，日志、持久化等文件会保存在这个目录
  dir .
  
  ################################# 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>
  #
  # However this is not enough if you are using Redis ACLs (for Redis version
  # 6 or greater), and the default user is not capable of running the PSYNC
  # command and/or other commands needed for replication. In this case it's
  # better to configure a special user to use with replication, and specify the
  # masteruser configuration as such:
  #
  # masteruser <username>
  #
  # When masteruser is specified, the replica will authenticate against its
  # master using the new AUTH form: AUTH <username> <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 commands except:
  #    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.
  #
  # 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
  
  # -----------------------------------------------------------------------------
  # WARNING: RDB diskless load is experimental. Since in this setup the replica
  # does not immediately store an RDB on disk, it may cause data loss during
  # failovers. RDB diskless load + Redis modules not handling I/O reads may also
  # cause Redis to abort in case of I/O errors during the initial synchronization
  # stage with the master. Use only if you know what you are doing.
  # -----------------------------------------------------------------------------
  #
  # Replica can load the RDB it reads from the replication link directly from the
  # socket, or store the RDB to a file and read that file after it was completely
  # received from the master.
  #
  # In many cases the disk is slower than the network, and storing and loading
  # the RDB file may increase replication time (and even increase the master's
  # Copy on Write memory and salve buffers).
  # However, parsing the RDB file directly from the socket may mean that we have
  # to flush the contents of the current database before the full rdb was
  # received. For this reason we have the following options:
  #
  # "disabled"    - Don't use diskless load (store the rdb file to the disk first)
  # "on-empty-db" - Use diskless load only when it is completely safe.
  # "swapdb"      - Keep a copy of the current db contents in RAM while parsing
  #                 the data directly from the socket. note that this requires
  #                 sufficient memory, if you don't have it, you risk an OOM kill.
  repl-diskless-load disabled
  
  # 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. The default
  # value is 60 seconds.
  #
  # 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 replica can endure the
  # disconnect and later be able to perform a partial resynchronization.
  #
  # The backlog is only allocated if there is at least one replica connected.
  #
  # repl-backlog-size 1mb
  
  # After a master has no 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 other 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
  
  # -----------------------------------------------------------------------------
  # By default, Redis Sentinel includes all replicas in its reports. A replica
  # can be excluded from Redis Sentinel's announcements. An unannounced replica
  # will be ignored by the 'sentinel replicas <master>' command and won't be
  # exposed to Redis Sentinel's clients.
  #
  # This option does not change the behavior of replica-priority. Even with
  # replica-announced set to 'no', the replica can be promoted to master. To
  # prevent this behavior, set replica-priority to 0.
  #
  # replica-announced yes
  
  # 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 address and port 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 actually be 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
  
  ############################### KEYS TRACKING #################################
  
  # Redis implements server assisted support for client side caching of values.
  # This is implemented using an invalidation table that remembers, using
  # a radix key indexed by key name, what clients have which keys. In turn
  # this is used in order to send invalidation messages to clients. Please
  # check this page to understand more about the feature:
  #
  #   https://redis.io/topics/client-side-caching
  #
  # When tracking is enabled for a client, all the read only queries are assumed
  # to be cached: this will force Redis to store information in the invalidation
  # table. When keys are modified, such information is flushed away, and
  # invalidation messages are sent to the clients. However if the workload is
  # heavily dominated by reads, Redis could use more and more memory in order
  # to track the keys fetched by many clients.
  #
  # For this reason it is possible to configure a maximum fill value for the
  # invalidation table. By default it is set to 1M of keys, and once this limit
  # is reached, Redis will start to evict keys in the invalidation table
  # even if they were not modified, just to reclaim memory: this will in turn
  # force the clients to invalidate the cached values. Basically the table
  # maximum size is a trade off between the memory you want to spend server
  # side to track information about who cached what, and the ability of clients
  # to retain cached objects in memory.
  #
  # If you set the value to 0, it means there are no limits, and Redis will
  # retain as many keys as needed in the invalidation table.
  # In the "stats" INFO section, you can find information about the number of
  # keys in the invalidation table at every given moment.
  #
  # Note: when key tracking is used in broadcasting mode, no memory is used
  # in the server side so this setting is useless.
  #
  # tracking-table-max-keys 1000000
  
  ################################## SECURITY ###################################
  
  # Warning: since Redis is pretty fast, an outside user can try up to
  # 1 million passwords per second against a modern box. This means that you
  # should use very strong passwords, otherwise they will be very easy to break.
  # Note that because the password is really a shared secret between the client
  # and the server, and should not be memorized by any human, the password
  # can be easily a long string from /dev/urandom or whatever, so by using a
  # long and unguessable password no brute force attack will be possible.
  
  # Redis ACL users are defined in the following format:
  #
  #   user <username> ... acl rules ...
  #
  # For example:
  #
  #   user worker +@list +@connection ~jobs:* on >ffa9203c493aa99
  #
  # The special username "default" is used for new connections. If this user
  # has the "nopass" rule, then new connections will be immediately authenticated
  # as the "default" user without the need of any password provided via the
  # AUTH command. Otherwise if the "default" user is not flagged with "nopass"
  # the connections will start in not authenticated state, and will require
  # AUTH (or the HELLO command AUTH option) in order to be authenticated and
  # start to work.
  #
  # The ACL rules that describe what a user can do are the following:
  #
  #  on           Enable the user: it is possible to authenticate as this user.
  #  off          Disable the user: it's no longer possible to authenticate
  #               with this user, however the already authenticated connections
  #               will still work.
  #  skip-sanitize-payload    RESTORE dump-payload sanitation is skipped.
  #  sanitize-payload         RESTORE dump-payload is sanitized (default).
  #  +<command>   Allow the execution of that command
  #  -<command>   Disallow the execution of that command
  #  +@<category> Allow the execution of all the commands in such category
  #               with valid categories are like @admin, @set, @sortedset, ...
  #               and so forth, see the full list in the server.c file where
  #               the Redis command table is described and defined.
  #               The special category @all means all the commands, but currently
  #               present in the server, and that will be loaded in the future
  #               via modules.
  #  +<command>|subcommand    Allow a specific subcommand of an otherwise
  #                           disabled command. Note that this form is not
  #                           allowed as negative like -DEBUG|SEGFAULT, but
  #                           only additive starting with "+".
  #  allcommands  Alias for +@all. Note that it implies the ability to execute
  #               all the future commands loaded via the modules system.
  #  nocommands   Alias for -@all.
  #  ~<pattern>   Add a pattern of keys that can be mentioned as part of
  #               commands. For instance ~* allows all the keys. The pattern
  #               is a glob-style pattern like the one of KEYS.
  #               It is possible to specify multiple patterns.
  #  allkeys      Alias for ~*
  #  resetkeys    Flush the list of allowed keys patterns.
  #  &<pattern>   Add a glob-style pattern of Pub/Sub channels that can be
  #               accessed by the user. It is possible to specify multiple channel
  #               patterns.
  #  allchannels  Alias for &*
  #  resetchannels            Flush the list of allowed channel patterns.
  #  ><password>  Add this password to the list of valid password for the user.
  #               For example >mypass will add "mypass" to the list.
  #               This directive clears the "nopass" flag (see later).
  #  <<password>  Remove this password from the list of valid passwords.
  #  nopass       All the set passwords of the user are removed, and the user
  #               is flagged as requiring no password: it means that every
  #               password will work against this user. If this directive is
  #               used for the default user, every new connection will be
  #               immediately authenticated with the default user without
  #               any explicit AUTH command required. Note that the "resetpass"
  #               directive will clear this condition.
  #  resetpass    Flush the list of allowed passwords. Moreover removes the
  #               "nopass" status. After "resetpass" the user has no associated
  #               passwords and there is no way to authenticate without adding
  #               some password (or setting it as "nopass" later).
  #  reset        Performs the following actions: resetpass, resetkeys, off,
  #               -@all. The user returns to the same state it has immediately
  #               after its creation.
  #
  # ACL rules can be specified in any order: for instance you can start with
  # passwords, then flags, or key patterns. However note that the additive
  # and subtractive rules will CHANGE MEANING depending on the ordering.
  # For instance see the following example:
  #
  #   user alice on +@all -DEBUG ~* >somepassword
  #
  # This will allow "alice" to use all the commands with the exception of the
  # DEBUG command, since +@all added all the commands to the set of the commands
  # alice can use, and later DEBUG was removed. However if we invert the order
  # of two ACL rules the result will be different:
  #
  #   user alice on -DEBUG +@all ~* >somepassword
  #
  # Now DEBUG was removed when alice had yet no commands in the set of allowed
  # commands, later all the commands are added, so the user will be able to
  # execute everything.
  #
  # Basically ACL rules are processed left-to-right.
  #
  # For more information about ACL configuration please refer to
  # the Redis web site at https://redis.io/topics/acl
  
  # ACL LOG
  #
  # The ACL Log tracks failed commands and authentication events associated
  # with ACLs. The ACL Log is useful to troubleshoot failed commands blocked 
  # by ACLs. The ACL Log is stored in memory. You can reclaim memory with 
  # ACL LOG RESET. Define the maximum entry length of the ACL Log below.
  acllog-max-len 128
  
  # Using an external ACL file
  #
  # Instead of configuring users here in this file, it is possible to use
  # a stand-alone file just listing users. The two methods cannot be mixed:
  # if you configure users here and at the same time you activate the external
  # ACL file, the server will refuse to start.
  #
  # The format of the external ACL user file is exactly the same as the
  # format that is used inside redis.conf to describe users.
  #
  # aclfile /etc/redis/users.acl
  
  # IMPORTANT NOTE: starting with Redis 6 "requirepass" is just a compatibility
  # layer on top of the new ACL system. The option effect will be just setting
  # the password for the default user. Clients will still authenticate using
  # AUTH <password> as usually, or more explicitly with AUTH default <password>
  # if they follow the new protocol: both will work.
  #
  # The requirepass is not compatable with aclfile option and the ACL LOAD
  # command, these will cause requirepass to be ignored.
  #
  requirepass requirepass 
  
  # New users are initialized with restrictive permissions by default, via the
  # equivalent of this ACL rule 'off resetkeys -@all'. Starting with Redis 6.2, it
  # is possible to manage access to Pub/Sub channels with ACL rules as well. The
  # default Pub/Sub channels permission if new users is controlled by the 
  # acl-pubsub-default configuration directive, which accepts one of these values:
  #
  # allchannels: grants access to all Pub/Sub channels
  # resetchannels: revokes access to all Pub/Sub channels
  #
  # To ensure backward compatibility while upgrading Redis 6.0, acl-pubsub-default
  # defaults to the 'allchannels' permission.
  #
  # Future compatibility note: it is very likely that in a future version of Redis
  # the directive's default of 'allchannels' will be changed to 'resetchannels' in
  # order to provide better out-of-the-box Pub/Sub security. Therefore, it is
  # recommended that you explicitly define Pub/Sub permissions for all users
  # rather then rely on implicit default values. Once you've set explicit
  # Pub/Sub for all existing users, you should uncomment the following line.
  #
  # acl-pubsub-default resetchannels
  
  # Command renaming (DEPRECATED).
  #
  # ------------------------------------------------------------------------
  # WARNING: avoid using this option if possible. Instead use ACLs to remove
  # commands from the default user, and put them only in some admin user you
  # create for administrative purposes.
  # ------------------------------------------------------------------------
  #
  # 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
  # minus 32 (as Redis reserves a few file descriptors for internal uses).
  #
  # Once the limit is reached Redis will close all the new connections sending
  # an error 'max number of clients reached'.
  #
  # IMPORTANT: When Redis Cluster is used, the max number of connections is also
  # shared with the cluster bus: every node in the cluster will use two
  # connections, one incoming and another outgoing. It is important to size the
  # limit accordingly in case of very large clusters.
  #
  # 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).
  #
  # If Redis can't remove keys according to the policy, or if the policy is
  # set to 'noeviction', Redis will start to reply with errors to commands
  # that would use more memory, like SET, LPUSH, and so on, and will continue
  # to reply to read-only commands like GET.
  #
  # This option is usually useful when using Redis as an LRU or LFU cache, or to
  # set a hard memory limit for an instance (using the 'noeviction' policy).
  #
  # 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
  # buffer of replicas is full with DELs of keys evicted triggering the deletion
  # of more keys, and so forth until the database is completely emptied.
  #
  # In short... if you have 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
  # output buffers (but this is not needed if the policy is 'noeviction').
  #
  # maxmemory <bytes>
  # 设置redis能够使用的最大内存
  maxmemory 512mb
  
  # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
  # is reached. You can select one from the following behaviors:
  #
  # volatile-lru -> Evict using approximated LRU, only keys with an expire set.
  # allkeys-lru -> Evict any key using approximated LRU.
  # volatile-lfu -> Evict using approximated LFU, only keys with an expire set.
  # allkeys-lfu -> Evict any key using approximated LFU.
  # volatile-random -> Remove a random key having an expire set.
  # allkeys-random -> Remove a random key, any key.
  # volatile-ttl -> Remove the key with the nearest expire time (minor TTL)
  # noeviction -> Don't 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.
  #
  # Note: with any of the above policies, when there are no suitable keys for
  # eviction, Redis will return an error on write operations that require
  # more memory. These are usually commands that create new keys, add data or
  # modify existing keys. A few examples are: SET, INCR, HSET, LPUSH, SUNIONSTORE,
  # SORT (due to the STORE argument), and EXEC (if the transaction includes any
  # command that requires memory).
  #
  # The default is:
  #
  # maxmemory-policy noeviction
  
  # LRU, LFU and minimal TTL algorithms are not precise algorithms but approximated
  # algorithms (in order to save memory), so you can tune it for speed or
  # accuracy. By default Redis will check five keys and pick the one that was
  # used least recently, you can change the sample size using the following
  # configuration directive.
  #
  # The default of 5 produces good enough results. 10 Approximates very closely
  # true LRU but costs more CPU. 3 is faster but not very accurate.
  #
  # maxmemory-samples 5
  
  # Eviction processing is designed to function well with the default setting.
  # If there is an unusually large amount of write traffic, this value may need to
  # be increased.  Decreasing this value may reduce latency at the risk of 
  # eviction processing effectiveness
  #   0 = minimum latency, 10 = default, 100 = process without regard to latency
  #
  # maxmemory-eviction-tenacity 10
  
  # Starting from Redis 5, by default a replica will ignore its maxmemory setting
  # (unless it is promoted to master after a failover or manually). It means
  # 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
  # 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
  
  # Redis reclaims expired keys in two ways: upon access when those keys are
  # found to be expired, and also in background, in what is called the
  # "active expire key". The key space is slowly and interactively scanned
  # looking for expired keys to reclaim, so that it is possible to free memory
  # of keys that are expired and will never be accessed again in a short time.
  #
  # The default effort of the expire cycle will try to avoid having more than
  # ten percent of expired keys still in memory, and will try to avoid consuming
  # more than 25% of total memory and to add latency to the system. However
  # it is possible to increase the expire "effort" that is normally set to
  # "1", to a greater value, up to the value "10". At its maximum value the
  # system will use more CPU, longer cycles (and technically may introduce
  # more latency), and will tolerate less already expired keys still present
  # in the system. It's a tradeoff between memory, CPU and latency.
  #
  # active-expire-effort 1
  
  ############################# LAZY FREEING ####################################
  
  # Redis has two primitives to delete keys. One is called DEL and is a blocking
  # 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
  # way. If the key deleted is associated with a small object, the time needed
  # 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
  # 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.
  # It's up to the design of the application to understand when it is a good
  # 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.
  # 2) Because of expire: when a key with an associated time to live (see the
  #    EXPIRE command) must be deleted from memory.
  # 3) Because of a side effect of a command that stores data on a key that may
  #    already exist. For example the RENAME command may delete the old key
  #    content when it is replaced with another one. Similarly SUNIONSTORE
  #    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
  #    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,
  # like if DEL was called. However you can configure each case specifically
  # 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
  
  # It is also possible, for the case when to replace the user code DEL calls
  # with UNLINK calls is not easy, to modify the default behavior of the DEL
  # command to act exactly like UNLINK, using the following configuration
  # directive:
  
  lazyfree-lazy-user-del no
  
  # FLUSHDB, FLUSHALL, and SCRIPT FLUSH support both asynchronous and synchronous
  # deletion, which can be controlled by passing the [SYNC|ASYNC] flags into the
  # commands. When neither flag is passed, this directive will be used to determine
  # if the data should be deleted asynchronously.
  
  lazyfree-lazy-user-flush no
  
  ################################ THREADED I/O #################################
  
  # Redis is mostly single threaded, however there are certain threaded
  # operations such as UNLINK, slow I/O accesses and other things that are
  # performed on side threads.
  #
  # Now it is also possible to handle Redis clients socket reads and writes
  # in different I/O threads. Since especially writing is so slow, normally
  # Redis users use pipelining in order to speed up the Redis performances per
  # core, and spawn multiple instances in order to scale more. Using I/O
  # threads it is possible to easily speedup two times Redis without resorting
  # to pipelining nor sharding of the instance.
  #
  # By default threading is disabled, we suggest enabling it only in machines
  # that have at least 4 or more cores, leaving at least one spare core.
  # Using more than 8 threads is unlikely to help much. We also recommend using
  # threaded I/O only if you actually have performance problems, with Redis
  # instances being able to use a quite big percentage of CPU time, otherwise
  # there is no point in using this feature.
  #
  # So for instance if you have a four cores boxes, try to use 2 or 3 I/O
  # threads, if you have a 8 cores, try to use 6 threads. In order to
  # enable I/O threads use the following configuration directive:
  #
  # io-threads 4
  #
  # Setting io-threads to 1 will just use the main thread as usual.
  # When I/O threads are enabled, we only use threads for writes, that is
  # to thread the write(2) syscall and transfer the client buffers to the
  # socket. However it is also possible to enable threading of reads and
  # protocol parsing using the following configuration directive, by setting
  # it to yes:
  #
  # io-threads-do-reads no
  #
  # Usually threading reads doesn't help much.
  #
  # NOTE 1: This configuration directive cannot be changed at runtime via
  # CONFIG SET. Aso this feature currently does not work when SSL is
  # enabled.
  #
  # NOTE 2: If you want to test the Redis speedup using redis-benchmark, make
  # sure you also run the benchmark itself in threaded mode, using the
  # --threads option to match the number of Redis threads, otherwise you'll not
  # be able to notice the improvements.
  
  ############################ KERNEL OOM CONTROL ##############################
  
  # On Linux, it is possible to hint the kernel OOM killer on what processes
  # should be killed first when out of memory.
  #
  # Enabling this feature makes Redis actively control the oom_score_adj value
  # for all its processes, depending on their role. The default scores will
  # attempt to have background child processes killed before all others, and
  # replicas killed before masters.
  #
  # Redis supports three options:
  #
  # no:       Don't make changes to oom-score-adj (default).
  # yes:      Alias to "relative" see below.
  # absolute: Values in oom-score-adj-values are written as is to the kernel.
  # relative: Values are used relative to the initial value of oom_score_adj when
  #           the server starts and are then clamped to a range of -1000 to 1000.
  #           Because typically the initial value is 0, they will often match the
  #           absolute values.
  oom-score-adj no
  
  # When oom-score-adj is used, this directive controls the specific values used
  # for master, replica and background child processes. Values range -2000 to
  # 2000 (higher means more likely to be killed).
  #
  # Unprivileged processes (not root, and without CAP_SYS_RESOURCE capabilities)
  # can freely increase their value, but not decrease it below its initial
  # settings. This means that setting oom-score-adj to "relative" and setting the
  # oom-score-adj-values to positive values will always succeed.
  oom-score-adj-values 0 200 800
  
  #################### KERNEL transparent hugepage CONTROL ######################
  
  # Usually the kernel Transparent Huge Pages control is set to "madvise" or
  # or "never" by default (/sys/kernel/mm/transparent_hugepage/enabled), in which
  # case this config has no effect. On systems in which it is set to "always",
  # redis will attempt to disable it specifically for the redis process in order
  # to avoid latency problems specifically with fork(2) and CoW.
  # If for some reason you prefer to keep it enabled, you can set this config to
  # "no" and the kernel global to "always".
  
  disable-thp yes
  
  ############################## APPEND ONLY MODE ###############################
  
  # By default Redis asynchronously dumps the dataset on disk. This mode is
  # good enough in many applications, but an issue with the Redis process or
  # 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
  # (see later in the config file) Redis can lose just one second of writes in a
  # 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.
  # If the AOF is enabled on startup Redis will load the AOF, that is the file
  # with the better durability guarantees.
  #
  # Please check https://redis.io/topics/persistence for more information.
  
  appendonly no
  
  # The name of the append only file (default: "appendonly.aof")
  
  appendfilename "appendonly.aof"
  
  # The fsync() call tells the Operating System to actually write data on disk
  # 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:
  #
  # no: don't fsync, just let the OS flush the data when it wants. Faster.
  # always: fsync after every write to the append only log. Slow, Safest.
  # everysec: fsync only one time every second. Compromise.
  #
  # The default is "everysec", as that's usually the right compromise between
  # speed and data safety. It's up to you to understand if you can relax this to
  # "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
  # 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.com/post/redis-persistence-demystified.html
  #
  # If unsure, use "everysec".
  
  # appendfsync always
  appendfsync everysec
  # appendfsync no
  
  # When the AOF fsync policy is set to always or everysec, and a background
  # saving process (a background save or AOF log background rewriting) is
  # performing a lot of I/O against the disk, in some Linux configurations
  # 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
  # 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
  # the same as "appendfsync none". In practical terms, this means that it is
  # 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.
  # 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
  # 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
  # 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.
  
  auto-aof-rewrite-percentage 100
  auto-aof-rewrite-min-size 64mb
  
  # An AOF file may be found to be truncated at the end during the Redis
  # startup process, when the AOF data gets loaded back into memory.
  # This may happen when the system where Redis is running
  # 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
  # data as possible (the default now) and start if the AOF file is found
  # 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
  # the Redis server starts emitting a log to inform the user of the event.
  # Otherwise if the option is set to no, the server aborts with an error
  # and refuses to start. When the option is set to no, the user requires
  # 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
  # the server will still exit with an error. This option only applies when
  # 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 file for faster rewrites and recoveries. When this option is turned
  # on the rewritten AOF file is composed of two different stanzas:
  #
  #   [RDB file][AOF tail]
  #
  # When loading, Redis recognizes that the AOF file starts with the "REDIS"
  # string and loads the prefixed RDB file, then continues loading the AOF
  # tail.
  aof-use-rdb-preamble yes
  
  ################################ LUA SCRIPTING  ###############################
  
  # 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 call any 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  ###############################
  
  # 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 a 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 * cluster-replica-validity-factor) + repl-ping-replica-period
  #
  # So for example if node-timeout is 30 seconds, and the cluster-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 cluster-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 cluster-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 or
  # set cluster-allow-replica-migration to 'no'.
  # A value of 0 can be set but is useful only for debugging and dangerous
  # in production.
  #
  # cluster-migration-barrier 1
  
  # Turning off this option allows to use less automatic cluster configuration.
  # It both disables migration to orphaned masters and migration from masters
  # that became empty.
  #
  # Default is 'yes' (allow automatic migrations).
  #
  # cluster-allow-replica-migration yes
  
  # By default Redis Cluster nodes stop accepting queries if they detect there
  # is at least a 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 replica 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
  
  # This option, when set to yes, allows nodes to serve read traffic while the
  # the cluster is in a down state, as long as it believes it owns the slots. 
  #
  # This is useful for two cases.  The first case is for when an application 
  # doesn't require consistency of data during node failures or network partitions.
  # One example of this is a cache, where as long as the node has the data it
  # should be able to serve it. 
  #
  # The second use case is for configurations that don't meet the recommended  
  # three shards but want to enable cluster mode and scale later. A 
  # master outage in a 1 or 2 shard configuration causes a read/write outage to the
  # entire cluster without this option set, with it set there is only a write outage.
  # Without a quorum of masters, slot ownership will not change automatically. 
  #
  # cluster-allow-reads-when-down no
  
  # In order to setup your cluster make sure to read the documentation
  # available at https://redis.io web site.
  
  ########################## CLUSTER DOCKER/NAT support  ########################
  
  # 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 four options are used for this scope, and are:
  #
  # * cluster-announce-ip
  # * cluster-announce-port
  # * cluster-announce-tls-port
  # * cluster-announce-bus-port
  #
  # Each instructs the node about its address, client ports (for connections
  # without and with TLS) 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 cluster-tls is set to yes and cluster-announce-tls-port is omitted or set
  # to zero, then cluster-announce-port refers to the TLS port. Note also that
  # cluster-announce-tls-port has no effect if cluster-tls is set to no.
  #
  # 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 usual.
  #
  # Example:
  #
  # cluster-announce-ip 10.1.1.5
  # cluster-announce-tls-port 6379
  # cluster-announce-port 0
  # 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 https://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)
  #  t     Stream commands
  #  d     Module key type events
  #  m     Key-miss events (Note: It is not included in the 'A' class)
  #  A     Alias for g$lshzxetd, so that the "AKE" string means all the events
  #        (Except key-miss events which are excluded from 'A' due to their
  #         unique nature).
  #
  #  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 ""
  
  ############################### GOPHER SERVER #################################
  
  # Redis contains an implementation of the Gopher protocol, as specified in
  # the RFC 1436 (https://www.ietf.org/rfc/rfc1436.txt).
  #
  # The Gopher protocol was very popular in the late '90s. It is an alternative
  # to the web, and the implementation both server and client side is so simple
  # that the Redis server has just 100 lines of code in order to implement this
  # support.
  #
  # What do you do with Gopher nowadays? Well Gopher never *really* died, and
  # lately there is a movement in order for the Gopher more hierarchical content
  # composed of just plain text documents to be resurrected. Some want a simpler
  # internet, others believe that the mainstream internet became too much
  # controlled, and it's cool to create an alternative space for people that
  # want a bit of fresh air.
  #
  # Anyway for the 10nth birthday of the Redis, we gave it the Gopher protocol
  # as a gift.
  #
  # --- HOW IT WORKS? ---
  #
  # The Redis Gopher support uses the inline protocol of Redis, and specifically
  # two kind of inline requests that were anyway illegal: an empty request
  # or any request that starts with "/" (there are no Redis commands starting
  # with such a slash). Normal RESP2/RESP3 requests are completely out of the
  # path of the Gopher protocol implementation and are served as usual as well.
  #
  # If you open a connection to Redis when Gopher is enabled and send it
  # a string like "/foo", if there is a key named "/foo" it is served via the
  # Gopher protocol.
  #
  # In order to create a real Gopher "hole" (the name of a Gopher site in Gopher
  # talking), you likely need a script like the following:
  #
  #   https://github.com/antirez/gopher2redis
  #
  # --- SECURITY WARNING ---
  #
  # If you plan to put Redis on the internet in a publicly accessible address
  # to server Gopher pages MAKE SURE TO SET A PASSWORD to the instance.
  # Once a password is set:
  #
  #   1. The Gopher server (when enabled, not by default) will still serve
  #      content via Gopher.
  #   2. However other commands cannot be called before the client will
  #      authenticate.
  #
  # So use the 'requirepass' option to protect your instance.
  #
  # Note that Gopher is not currently supported when 'io-threads-do-reads'
  # is enabled.
  #
  # To enable Gopher support, uncomment the following line and set the option
  # from no (the default) to yes.
  #
  # gopher-enabled no
  
  ############################### 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 entries 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 to 512 mb. However you can change this limit
  # here, but must be 1mb or greater
  #
  # 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 temporarily raise when there are many connected clients.
  #
  # When dynamic HZ is enabled, the actual configured HZ will be used
  # 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 #######################
  #
  # 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 a "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 no
  
  # 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, to be used when the lower
  # threshold is reached
  # active-defrag-cycle-min 1
  
  # Maximal effort for defrag in CPU percentage, to be used when the upper
  # threshold is reached
  # active-defrag-cycle-max 25
  
  # Maximum number of set/hash/zset/list fields that will be processed from
  # the main dictionary scan
  # active-defrag-max-scan-fields 1000
  
  # Jemalloc background thread for purging will be enabled by default
  jemalloc-bg-thread yes
  
  # It is possible to pin different threads and processes of Redis to specific
  # CPUs in your system, in order to maximize the performances of the server.
  # This is useful both in order to pin different Redis threads in different
  # CPUs, but also in order to make sure that multiple Redis instances running
  # in the same host will be pinned to different CPUs.
  #
  # Normally you can do this using the "taskset" command, however it is also
  # possible to this via Redis configuration directly, both in Linux and FreeBSD.
  #
  # You can pin the server/IO threads, bio threads, aof rewrite child process, and
  # the bgsave child process. The syntax to specify the cpu list is the same as
  # the taskset command:
  #
  # Set redis server/io threads to cpu affinity 0,2,4,6:
  # server_cpulist 0-7:2
  #
  # Set bio threads to cpu affinity 1,3:
  # bio_cpulist 1,3
  #
  # Set aof rewrite child process to cpu affinity 8,9,10,11:
  # aof_rewrite_cpulist 8-11
  #
  # Set bgsave child process to cpu affinity 1,10,11
  # bgsave_cpulist 1,10-11
  
  # In some cases redis will emit warnings and even refuse to start if it detects
  # that the system is in bad state, it is possible to suppress these warnings
  # by setting the following config which takes a space delimited list of warnings
  # to suppress
  #
  # ignore-warnings ARM64-COW-BUG
  
  

Redis的其它常见配置

# 监听的地址，默认是127.0.0.1，会导致只能在本地访问。修改为0.0.0.0则可以在任意IP访问，生产环境不要设置为0.0.0.0
bind 0.0.0.0
# 守护进程，修改为yes后即可后台运行
daemonize yes
# 密码，设置后访问Redis必须输入密码
requirepass pwd123456
# 监听的端口
port 6379
#工作目录，默认是当前目录，也就是运行redis-server时的命令，日志、持久化等文件会保存在这个目录
dir .
# 数据库数量，设置为16，代表使用16个库，默认有16个库，编号0~15
databases 16
# 设置redis能够使用的最大内存
maxmemory 512mb
# 日志文件，默认为空，不记录日志，可以指定日志文件名
logfile "redis.log"

创建并运行新redis容器，挂载本地目录

docker run -d \
	--restart=always \
	--name redis \
	-p 6379:6379 \
	-v /usr/local/docker_data/redis/conf:/etc/redis/redis.conf \
	-v /usr/local/docker_data/redis/data:/data \
	redis:7.0.12 redis-server /etc/redis/redis.conf
	

1.1.3部署 MySQL

1.简易安装

而使用 Docker 安装，仅仅需要一步即可，在命令行输入下面的命令（建议采用 CV 大法）：

docker run -d \
  --name mysql \
  --restart=always \
  -p 3306:3306 \
  -e TZ=Asia/Shanghai \
  -e MYSQL_ROOT_PASSWORD=123456 \
  mysql:5.7

2.挂载数据卷安装

提前创建对应文件夹

##一次性创建
mkdir -p /usr/local/docker_data/mysql/data && mkdir -p /usr/local/docker_data/mysql/conf     && mkdir -p /usr/local/docker_data/mysql/logs


##分步创建
# 宿主机创建数据存放目录映射到容器
mkdir -p /usr/local/docker_data/mysql/data

# 宿主机创建配置文件目录映射到容器 
mkdir -p /usr/local/docker_data/mysql/conf #(需要在此目录下创建"conf.d"、"mysql.conf.d"两个目录)
### mkdir -p /usr/local/docker_data/mysql/conf/conf.d # (建议在此目录创建my.cnf文件并进行相关MySQL配置)
### mkdir -p /usr/local/docker_data/mysql/conf/mysql.conf.d

# 宿主机创建日志目录映射到容器
mkdir -p /usr/local/docker_data/mysql/logs

在 /usr/local/docker_data/mysql/conf 文件夹内建一个my.cnf文件

vim /usr/local/docker_data/mysql/conf/my.cnf

[mysqld]
user=mysql
character-set-server=utf8
default_authentication_plugin=mysql_native_password
secure_file_priv=/var/lib/mysql
expire_logs_days=7
sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION
max_connections=1000
[client]
default-character-set=utf8
[mysql]
default-character-set=utf8

创建并运行新mysql容器，挂载本地目录

docker run -d \
  --restart=always \
  --name mysql \
  -p 3306:3306 \
  -e TZ=Asia/Shanghai \
  -e MYSQL_ROOT_PASSWORD=123456 \
  -v /usr/local/docker_data/mysql/data:/var/lib/mysql \
  -v /usr/local/docker_data/mysql/conf:/etc/mysql \
  -v /usr/local/docker_data/mysql/conf/my.cnf:/etc/mysql/my.cnf \
  -v /usr/local/docker_data/mysql/logs:/var/log/mysql\
  mysql:5.7

进入mysql容器

docker exec -it mysql bash

登录mysql

mysql -u root -p

登录成功后，输入修改密码指令

alter user 'root'@'localhost' identified by '123456';

使其他电脑可以远程访问mysql数据库

GRANT ALL ON *.* TO 'root'@'%' IDENTIFIED BY '123456';

使设置生效

flush privileges;

进入mysql查看 my.cnf配置是否生效 字符集是否设置成功。

show variables like 'char%';

mysql> show variables like 'char%';
+--------------------------+----------------------------+
| Variable_name            | Value                      |
+--------------------------+----------------------------+
| character_set_client     | utf8                       |
| character_set_connection | utf8                       |
| character_set_database   | utf8                       |
| character_set_filesystem | binary                     |
| character_set_results    | utf8                       |
| character_set_server     | utf8                       |
| character_set_system     | utf8                       |
| character_sets_dir       | /usr/share/mysql/charsets/ |
+--------------------------+----------------------------+
8 rows in set (0.01 sec)

show variables like 'coll%';

mysql> show variables like 'coll%';
+----------------------+-----------------+
| Variable_name        | Value           |
+----------------------+-----------------+
| collation_connection | utf8_general_ci |
| collation_database   | utf8_general_ci |
| collation_server     | utf8_general_ci |
+----------------------+-----------------+
3 rows in set (0.01 sec)

退出mysql指令模式

exit

---

---

MySQL配置文件my.cnf各参数详解

# +--------------+
# | 客户端基本设置 |
# +--------------+
[client]

# 默认连接端口
port = 3306

# 用于本地连接的socket套接字
socket = /usr/local/mysql/data/mysql.sock

# 编码
default-character-set = utf8mb4

# +--------------+
# | 服务端基本设置 |
# +--------------+
[mysqld] 

# MySQL监听端口
port = 3306

# 为MySQL客户端程序和服务器之间的本地通讯指定一个套接字文件
socket = /usr/local/mysql/data/mysql.sock

# pid文件所在目录
pid-file = /usr/local/mysql/data/mysql.pid

# 使用该目录作为根目录（安装目录）
basedir = /usr/local/mysql

# 数据文件存放的目录
datadir = /usr/local/mysql/database

# MySQL存放临时文件的目录
tmpdir = /usr/local/mysql/data/tmp

# 服务端默认编码（数据库级别）
character_set_server = utf8mb4

# 服务端默认的比对规则，排序规则
collation_server = utf8mb4_bin

# MySQL启动用户。如果是root用户就配置root，mysql用户就配置mysql
user = root

# 错误日志配置文件(configure file)
log-error=/usr/local/mysql/data/error.log

# 设置允许 load data导入、导出的位置
secure-file-priv = ''

# 开启了binlog后，必须设置这个值为1.主要是考虑binlog安全
# 此变量适用于启用二进制日志记录的情况。它控制是否可以信任存储函数创建者，
# 而不是创建将导致要写入二进制日志的不安全事件。如果设置为0（默认值），
# 则不允许用户创建或更改存储函数，除非用户具有
# 除创建例程或更改例程特权之外的特权 
log_bin_trust_function_creators = 1

# 性能优化的引擎，默认关闭
performance_schema = 0

# 开启全文索引
ft_min_word_len = 1

# 自动修复MySQL的myisam表
myisam_recover

# 明确时间戳默认null方式
explicit_defaults_for_timestamp

# 计划任务（事件调度器）
event_scheduler

# 跳过外部锁定;External-locking用于多进程条件下为MyISAM数据表进行锁定
skip-external-locking

# 跳过客户端域名解析；当新的客户连接mysqld时，
# mysqld创建一个新的线程来处理请求。
# 该线程先检查是否主机名在主机名缓存中。如果不在，线程试图解析主机名。
# 
# 使用这一选项以消除MySQL进行DNS解析的时间。但需要注意，如果开启该选项，
# 则所有远程主机连接授权都要使用IP地址方式，否则MySQL将无法正常处理连接请求!
skip-name-resolve

# MySQL绑定IP
# 1.这个bind-address强烈推荐不配置 
# 
# 2.如果要配置bind-address的话，这个localhost不能修改，
#  否则在初始化数据库(执行/opt/cloudera/cm/schema/scm_prepare_database.sh 
#  mysql cm cm password)时便会报错
#  如果配置了localhost的话，那么在CDH的安装页面中，配置连接数据库的主机名称必须为localhost  
# 
# 3.强烈不推荐写bind-address=xxx，
#  那么后面的CDH安装对应的组件时要填写的“数据库主机名称”默认使用主机名。
# 
# 4.如果/etc/my.cnf中配置了bind-address=localhost 的话，
#  那么在CDH的安装页面中，配置连接数据库的主机名称必须为localhost。
#  缺点：但是在安装hue时，“数据库主机名称”并无法使用localhost或任何主机名，所以造成无法安装hue
# 
# 5.不配置 bind-address=localhost 的话，则使用主机名(NDOE1)作为此处的数据库主机名称
bind-address=localhost  

# 为了安全起见，复制环境的数据库还是设置--skip-slave-start参数，防止复制随着mysql启动而自动启动
skip-slave-start

# 在中止读取之前等待来自主/从连接的更多数据的秒数。 MySQL主从复制的时候，
# 当Master和Slave之间的网络中断，但是Master和Slave无法察觉的情况下（比如防火墙或者路由问题）。
# Slave会等待slave_net_timeout设置的秒数后，
# 才能认为网络出现故障，然后才会重连并且追赶这段时间主库的数据。
# 
# 1.用这三个参数来判断主从是否延迟是不准确的Slave_IO_Running,Slave_SQL_Running,
#  Seconds_Behind_Master.还是用pt-heartbeat吧。
# 2.slave_net_timeout不要用默认值，设置一个你能接受的延时时间。
slave_net_timeout = 30

# 设定是否支持命令load data local infile。如果指定local关键词，则表明支持从客户主机读文件
local-infile = 0

# 指定MySQL可能的连接数量。
# 当MySQL主线程在很短的时间内得到非常多的连接请求，该参数就起作用，
# 之后主线程花些时间（尽管很短）检查连接并且启动一个新线程。
# 
# back_log参数的值指出在MySQL暂时停止响应新请求之前的短时间内多少个请求可以被存在堆栈中。
back_log = 1024

# sql_mode是一组语法校验规则
# 常用的参数有:
# 	ONLY_FULL_GROUP_BY
# 	(对于GROUP BY聚合操作，如果在SELECT中的列，没有在GROUP BY中出现，
# 	那么这# 个SQL是不合法的，因为列不在GROUP BY从句中)
# 
# 	NO_AUTO_VALUE_ON_ZERO
# 	(该值影响自增长列的插入。默认设置下，插入0或NULL代表生成下一个自增长值。
# 	如果用户希望插入的值为0，而该列又是自增长的，那么这个选项就有用了。)
# 
# 	STRICT_TRANS_TABLES  
# 	(如果一个值不能插入到一个事务中，则中断当前的操作，对非事务表不做限制)
# 
# 	NO_ZERO_IN_DATE  (不允许日期和月份为零)
# 
# 	NO_ZERO_DATE 
# 	(mysql数据库不允许插入零日期，插入零日期会抛出错误而不是警告)
# 
# 	ERROR_FOR_DIVISION_BY_ZERO 
# 	(在insert或update过程中，如果数据被零除，则产生错误而非警告。
# 	如果未给出该模式，那么数据被零除时Mysql返回NULL)
# 
# 	NO_AUTO_CREATE_USER	
# 	(禁止GRANT创建密码为空的用户 MySQL8.0已取消配置将无法启动)
# 
# 	NO_ENGINE_SUBSTITUTION 
# 	(如果需要的存储引擎被禁用或未编译，那么抛出错误。
# 	不设置此值时，用默认的存储引擎替代，并抛出一个异常)
# 
# 	PIPES_AS_CONCAT 
# 	(将"||"视为字符串的连接操作符而非或运算符，
# 	这和Oracle数据库是一样是，也和字符串的拼接函数Concat想类似)
# 
# 	ANSI_QUOTES  (不能用双引号来引用字符串，因为它被解释为识别符)
sql_mode = PIPES_AS_CONCAT,ANSI_QUOTES,IGNORE_SPACE,NO_KEY_OPTIONS,NO_TABLE_OPTIONS,NO_FIELD_OPTIONS,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

# 索引块的缓冲区大小，对MyISAM表性能影响最大的一个参数.决定索引处理的速度，
# 尤其是索引读的速度。默认值是16M，通过检查状态值Key_read_requests
# 
# 和Key_reads，可以知道key_buffer_size设置是否合理
key_buffer_size = 32M

# 一个查询语句包的最大尺寸。消息缓冲区被初始化为net_buffer_length字节，
# 但是可在需要时增加到max_allowed_packet个字节。
# 
# 该值太小则会在处理大包时产生错误。如果使用大的BLOB列，必须增加该值。
# 
# 这个值来限制server接受的数据包大小。
# 有时候大的插入和更新会受max_allowed_packet 参数限制，导致写入或者更新失败。
max_allowed_packet = 512M

# 线程缓存；主要用来存放每一个线程自身的标识信息，
# 如线程id，线程运行时基本信息等等，
# 我们可以通过 thread_stack 参数来设置为每一个线程栈分配多大的内存。
thread_stack = 256K

# 是MySQL执行排序使用的缓冲大小。
# 如果想要增加ORDER BY的速度，首先看是否可以让MySQL使用索引而不是额外的排序阶段。
# 如果不能，可以尝试增加sort_buffer_size变量的大小。
sort_buffer_size = 16M

# 是MySQL读入缓冲区大小。对表进行顺序扫描的请求将分配一个读入缓冲区，
# MySQL会为它分配一段内存缓冲区。read_buffer_size变量控制这一缓冲区的大小。
# 
# 如果对表的顺序扫描请求非常频繁，并且你认为频繁扫描进行得太慢，
# 可以通过增加该变量值以及内存缓冲区大小提高其性能。
read_buffer_size = 16M

# 应用程序经常会出现一些两表（或多表）Join的操作需求，
# MySQL在完成某些 Join 需求的时候（all/index join），为了减少参与Join的“被驱动表”
# 的读取次数以提高性能，需要使用到 Join Buffer 来协助完成 Join操作。
# 当 Join Buffer 太小，MySQL 不会将该 Buffer 存入磁盘文件，
# 而是先将Join Buffer中的结果集与需要 Join 的表进行 Join 操作，
# 然后清空 Join Buffer 中的数据，继续将剩余的结果集写入此 Buffer 中，
# 如此往复。这势必会造成被驱动表需要被多次读取，成倍增加 IO 访问，降低效率。
join_buffer_size = 16M

# 是MySQL的随机读缓冲区大小。当按任意顺序读取行时(例如，按照排序顺序)，
# 将分配一个随机读缓存区。进行排序查询时，MySQL会首先扫描一遍该缓冲，以避免磁盘搜索，
# 提高查询速度，如果需要排序大量数据，可适当调高该值。
# 但MySQL会为每个客户连接发放该缓冲空间，所以应尽量适当设置该值，以避免内存开销过大。
read_rnd_buffer_size = 32M

# 通信缓冲区在查询期间被重置到该大小。通常不要改变该参数值，
# 但是如果内存不足，可以将它设置为查询期望的大小。
# （即，客户发出的SQL语句期望的长度。如果语句超过这个长度，
# 缓冲区自动地被扩大，直到max_allowed_packet个字节。）
net_buffer_length = 16K

# 当对MyISAM表执行repair table或创建索引时，用以缓存排序索，
# 设置太小时可能会遇到” myisam_sort_buffer_size is too small”
myisam_sort_buffer_size = 128M

# 默认8M，当对MyISAM非空表执行insert … select/ insert … values(…),(…)或者load data infile时，
# 使用树状cache缓存数据，每个thread分配一个；
# 注：当对MyISAM表load 大文件时，
# 调大bulk_insert_buffer_size/myisam_sort_buffer_size/key_buffer_size会极大提升速度
bulk_insert_buffer_size = 32M

# thread_cahe_size线程池，线程缓存。用来缓存空闲的线程，
# 以至于不被销毁，如果线程缓存在的空闲线程，需要重新建立新连接，
# 则会优先调用线程池中的缓存，
# 很快就能响应连接请求。每建立一个连接，都需要一个线程与之匹配。
thread_cache_size = 384

# 工作原理： 一个SELECT查询在DB中工作后，DB会把该语句缓存下来，
# 当同样的一个SQL再次来到DB里调用时，
# DB在该表没发生变化的情况下把结果从缓存中返回给Client。
# 在数据库写入量或是更新量也比较大的系统，该参数不适合分配过大。
# 而且在高并发，写入量大的系统，建系把该功能禁掉。
query_cache_size = 0

# 决定是否缓存查询结果。这个变量有三个取值：0,1,2，分别代表了off、on、demand。
query_cache_type = 0

# 它规定了内部内存临时表的最大值，每个线程都要分配。
# （实际起限制作用的是tmp_table_size和max_heap_table_size的最小值。）
# 如果内存临时表超出了限制，MySQL就会自动地把它转化为基于磁盘的MyISAM表，存储在指定的tmpdir目录下
tmp_table_size = 1024M

# 独立的内存表所允许的最大容量.
# 此选项为了防止意外创建一个超大的内存表导致永尽所有的内存资源.
max_heap_table_size = 512M

# mysql打开最大文件数
open_files_limit = 10240

# MySQL无论如何都会保留一个用于管理员（SUPER）登陆的连接，
# 用于管理员连接数据库进行维护操作，即使当前连接数已经达到了max_connections。
# 
# 因此MySQL的实际最大可连接数为max_connections+1；
# 这个参数实际起作用的最大值（实际最大可连接数）为16384，
# 即该参数最大值不能超过16384，即使超过也以16384为准；
# 
# 增加max_connections参数的值，不会占用太多系统资源。
# 系统资源（CPU、内存）的占用主要取决于查询的密度、效率等；
# 
# 该参数设置过小的最明显特征是出现”Too many connections”错误；
max_connections = 2000

# 用来限制用户资源的，0不限制；对整个服务器的用户限制
max-user-connections = 0

# max_connect_errors是一个MySQL中与安全有关的计数器值，
# 它负责阻止过多尝试失败的客户端以防止暴力破解密码的情况。
# max_connect_errors的值与性能并无太大关系。
# 当此值设置为10时，意味着如果某一客户端尝试连接此MySQL服务器，
# 但是失败（如密码错误等等）10次，则MySQL会无条件强制阻止此客户端连接。
max_connect_errors = 100000

# 表描述符缓存大小，可减少文件打开/关闭次数；
table_open_cache = 5120

# 指的是mysql在关闭一个交互的连接之前所要等待的秒数
# (交互连接如mysql gui tool中的连接超时时间)
# (通过mysql客户端连接数据库是交互式连接，通过jdbc连接数据库是非交互式连接)
interactive_timeout = 86400

# 指的是MySQL在关闭一个非交互的连接超时要等待的秒数
# (通过mysql客户端连接数据库是交互式连接，通过jdbc连接数据库是非交互式连接)
wait_timeout = 86400

# 二进制日志缓冲大小
# 我们知道InnoDB存储引擎是支持事务的，实现事务需要依赖于日志技术，为了性能，
# 日志编码采用二进制格式。那么，我们如何记日志呢？有日志的时候，就直接写磁盘？
# 可是磁盘的效率是很低的，如果你用过Nginx，，一般Nginx输出access log都是要缓冲输出的。
# 因此，记录二进制日志的时候，我们是否也需要考虑Cache呢？
# 答案是肯定的，但是Cache不是直接持久化，于是面临安全性的问题——因为系统宕机时，
# Cache中可能有残余的数据没来得及写入磁盘。因此，Cache要权衡，要恰到好处：
# 既减少磁盘I/O，满足性能要求；又保证Cache无残留，及时持久化，满足安全要求。
binlog_cache_size = 16M

# 开启慢查询
slow_query_log = true

# 慢查询地址
slow_query_log_file = /usr/local/mysql/data/slow_query_log.log

# 超过的时间为1s；MySQL能够记录执行时间超过参数 long_query_time 设置值的SQL语句，默认是不记录的。
long_query_time = 1

# 开启记录管理型慢SQL
log-slow-admin-statements

# 记录管理语句和没有使用index的查询记录
log-queries-not-using-indexes

# +--------------+
# |  主从复制配置  |
# +--------------+ start.

# 在复制方面的改进就是引进了新的复制技术：基于行的复制。
# 简言之，这种新技术就是关注表中发生变化的记录，而非以前的照抄 binlog 模式。
#
# 从 MySQL 5.1.12 开始，可以用以下三种模式来实现：
#	-基于SQL语句的复制(statement-based replication, SBR)，
# 	-基于行的复制(row-based replication, RBR)，
#	-混合模式复制(mixed-based replication, MBR)。
#
# 相应地，binlog的格式也有三种：STATEMENT，ROW，MIXED。
# MBR 模式中，SBR 模式是默认的。
binlog_format = ROW

# 为每个session 最大可分配的内存，在事务过程中用来存储二进制日志的缓存。
# max_binlog_cache_size = 102400

# 开启二进制日志功能，binlog数据位置
log-bin = /usr/local/mysql/data/binlog/mysql-bin

# binlog文件的索引文件，这个文件管理了所有的binlog文件的目录
log-bin-index = /usr/local/mysql/data/binlog/mysql-bin.index

# relay-log日志记录的是从服务器I/O线程将主服务器的二进制日志读取过来记录到从服务器本地文件，
# 然后SQL线程会读取relay-log日志的内容并应用到从服务器
relay-log = /usr/local/mysql/data/relay/mysql-relay-bin

# binlog传到备机被写道relaylog里，备机的slave sql线程从relaylog里读取然后应用到本地。
relay-log-index = /usr/local/mysql/data/relay/mysql-relay-bin.index
# ==================================================================

#**************
# 主服务器配置
#**************

# 服务端ID，用来高可用时做区分
server-id = 1

# 指定 database 不被记录binlog
# 不同步哪些数据库，除此之外，其他不同步
# ("binlog-ignore-db"和"binlog-do-db"为互斥关系，一般只选择其一设置)
binlog-ignore-db = mysql
binlog-ignore-db = sys
binlog-ignore-db = binlog
binlog-ignore-db = relay
binlog-ignore-db = tmp
binlog-ignore-db = test
binlog-ignore-db = information_schema
binlog-ignore-db = performance_schema

# 指定 database 记录binlog
# 同步哪些数据库
# ("binlog-ignore-db"和"binlog-do-db"为互斥关系，一般只选择其一设置)
binlog-do-db = db_1
binlog-do-db = db_2

#**************
# 从服务器配置
#**************

# 服务端ID，用来高可用时做区分
server-id = 2

# 不要需要同步的database
replicate-ignore-db = mysql
replicate-ignore-db = sys
replicate-ignore-db = relay
replicate-ignore-db = tmp
replicate-ignore-db = test
replicate-ignore-db = information_schema
replicate-ignore-db = performance_schema

# 需要同步的database
# 只同步哪些数据库，除此之外，其他不同步
replicate-do-db = db_1
replicate-do-db = db_2

# ==================================================================

# 将从服务器从主服务器收到的更新记入到从服务器自己的二进制日志文件中。
log_slave_updates = 1

# 二进制日志自动删除的天数。默认值为0,表示“没有自动删除”。启动时和二进制日志循环时可能删除。
expire-logs-days = 15

# 如果二进制日志写入的内容超出给定值，日志就会发生滚动。
# 你不能将该变量设置为大于1GB或小于4096字节。 默认值是1GB。
max_binlog_size = 128M

# 同步所有跨数据库的更新，比如replicate-do-db或者replicate-ignore-db不会同步类似
# replicate-wild-ignore-table = mysql.%

# 设定需要同步的Table
replicate-wild-do-table = db_name.%

# 复制时跳过一些错误;不要胡乱使用这些跳过错误的参数，
# 除非你非常确定你在做什么。当你使用这些参数时候，MYSQL会忽略那些错误，
# 这样会导致你的主从服务器数据不一致。
slave-skip-errors = 1062,1053,1146

# 表示id的起始值从1开始增长(但不表示第一个id就是1)
auto_increment_offset = 1

# 表示id的增长偏移量为2，就是下一个id比上一个id大2
auto_increment_increment = 2

# 将中继日志的信息写入表:mysql.slave_realy_log_info
relay_log_info_repository = TABLE

# 将master的连接信息写入表：mysql.salve_master_info
master_info_repository = TABLE

# 中继日志自我修复；当slave从库宕机后，假如relay-log损坏了，
# 导致一部分中继日志没有处理，则自动放弃所有未执行的relay-log，
# 并且重新从master上获取日志，这样就保证了relay-log的完整性
relay_log_recovery = on

# +--------------+
# |  主从复制配置  |
# +--------------+ end.

# +--------------+
# |  innodb设置   |
# +--------------+ 

# InnoDB 用来高速缓冲数据和索引内存缓冲大小。 更大的设置可以使访问数据时减少磁盘 I/O。
innodb_buffer_pool_size = 128M

# 单独指定数据文件的路径与大小
innodb_data_file_path = ibdata1:10M:autoextend

# 每次commit 日志缓存中的数据刷到磁盘中。通常设置为 1，
# 意味着在事务提交前日志已被写入磁盘,事务可以运行更长以及服务崩溃后的修复能力。
# 如果你愿意减弱这个安全，或你运行的是比较小的事务处理，
# 可以将它设置为 0 ，以减少写日志文件的磁盘 I/O。这个选项默认设置为 0。
innodb_flush_log_at_trx_commit = 2

# sync_binlog：这个参数是对于MySQL系统来说是至关重要的，
# 他不仅影响到Binlog对MySQL所带来的性能损耗，而且还影响到MySQL中数据的完整性。
#	sync_binlog=0
#	(当事务提交之后，MySQL不做fsync之类的磁盘同步指令刷新binlog_cache中的信息到磁盘，
#	而让Filesystem自行决定什么时候来做同步，或者cache满了之后才同步到磁盘)
#
#	sync_binlog=n
#	(当每进行n次事务提交之后，MySQL将进行一次fsync之类的磁盘同步指令来将binlog_cache中的数据强制写入磁盘。)
sync_binlog=0

# 读线程个数，默认是4个(可根据CPU核心数配置)
innodb_read_io_threads = 8

# 写线程个数，默认是4个(可根据CPU核心数配置)
innodb_write_io_threads = 8

# 限制Innodb能打开的表的数量
innodb_open_files = 1000

# 开始碎片回收线程。这个应该能让碎片回收得更及时而且不影响其他线程的操作
innodb_purge_threads = 1

# InnoDB 将日志写入日志磁盘文件前的缓冲大小。理想值为 1M 至 8M。
# 大的日志缓冲允许事务运行时不需要将日志保存入磁盘而只到事务被提交(commit)。
# 因此，如果有大的事务处理，设置大的日志缓冲可以减少磁盘I/O。
innodb_log_buffer_size = 8M

# 日志组中的每个日志文件的大小(单位 MB)。如果 n 是日志组中日志文件的数目，
# 那么理想的数值为 1M 至下面设置的缓冲池(buffer pool)大小的 1/n。较大的值，
# 可以减少刷新缓冲池的次数，从而减少磁盘 I/O。
# 但是大的日志文件意味着在崩溃时需要更长的时间来恢复数据。
innodb_log_file_size = 128M

# 指定有三个日志组
innodb_log_files_in_group = 3

# 在回滚(rooled back)之前，InnoDB 事务将等待超时的时间(单位 秒)
innodb_lock_wait_timeout = 120

# innodb_max_dirty_pages_pct作用：控制Innodb的脏页在缓冲中在那个百分比之下，
# 值在范围1-100,默认为90.这个参数的另一个用处：
# 当Innodb的内存分配过大，致使swap占用严重时，可以适当的减小调整这个值，
# 使达到swap空间释放出来。建义：这个值最大在90%，最小在15%。
# 太大，缓存中每次更新需要致换数据页太多，太小，放的数据页太小，更新操作太慢。
innodb_max_dirty_pages_pct = 75

# innodb_buffer_pool_size 一致 可以开启多个内存缓冲池，
# 把需要缓冲的数据hash到不同的缓冲池中，这样可以并行的内存读写。
innodb_buffer_pool_instances = 4

# innodb刷新脏页的能力
# 这个参数据控制Innodb checkpoint时的IO能力
innodb_io_capacity = 500

# 作用：使每个Innodb的表，有自已独立的表空间。如删除文件后可以回收那部分空间。
# 分配原则：只有使用不使用。但ＤＢ还需要有一个公共的表空间。
innodb_file_per_table = 1

# 当更新/插入的非聚集索引的数据所对应的页不在内存中时（对非聚集索引的更新操作通常会带来随机IO），
# 会将其放到一个insert buffer中，当随后页面被读到内存中时，会将这些变化的记录merge到页中。
# 当服务器比较空闲时，后台线程也会做merge操作
innodb_change_buffering = inserts

# 该值影响每秒刷新脏页的操作，开启此配置后，
# 刷新脏页会通过判断产生重做日志的速度来判断最合适的刷新脏页的数量；
innodb_adaptive_flushing = 1

# 数据库事务隔离级别 ，读取提交内容
transaction-isolation = READ-COMMITTED

# 控制着innodb数据文件及redo log的打开、刷写模式
# InnoDB使用O_DIRECT模式打开数据文件，用fsync()函数去更新日志和数据文件。
innodb_flush_method = fsync

# 默认设置值为1.设置为0：表示Innodb使用自带的内存分配程序；
# 设置为1：表示InnoDB使用操作系统的内存分配程序。
innodb_use_sys_malloc = 1

# +--------------+
# |  逻辑备份设置  |
# +--------------+ 
[mysqldump]

# 它强制 mysqldump 从服务器查询取得记录直接输出而不是取得所有记录后将它们缓存到内存中
quick

# 限制server接受的数据包大小;指代mysql服务器端和客户端在一次传送数据包的过程当中数据包的大小
max_allowed_packet = 512M

# TCP/IP和套接字通信缓冲区大小,创建长度达net_buffer_length的行
net_buffer_length = 16384

[mysql]
# auto-rehash是自动补全的意思
auto-rehash

# isamchk数据检测恢复工具
[isamchk]

key_buffer = 256M

sort_buffer_size = 256M

read_buffer = 2M

write_buffer = 2M

# 使用myisamchk实用程序来获得有关你的数据库桌表的信息、检查和修复他们或优化他们
# myisamchk默认只用3M的内存来修复，如果要修复大表的话，
# 显然速度会巨慢，我们可以通过为myisamchk设置更多的内存，来使其运行的更快，
[myisamchk]

key_buffer = 256M
sort_buffer_size = 256M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]

# mysqlhotcopy使用lock tables、flush tables和cp或scp来快速备份数据库.
# 它是备份数据库或单个表最快的途径,完全属于物理备份,
# 但只能用于备份MyISAM存储引擎和运行在数据库目录所在的机器上.
# 与mysqldump备份不同,mysqldump属于逻辑备份,备份时是执行的sql语句.
# 使用mysqlhotcopy命令前需要要安装相应的软件依赖包
interactive-timeout

1.1.4 部署 Seata（分布式事务）

1. 简易安装

docker run -d \
--name seata \
--restart=always \
-p 8099:8099 \
-p 7099:7099 \
seataio/seata-server:1.5.2

2. 挂载数据卷安装

提前创建对应文件夹

mkdir -p /usr/local/docker_data/seata

创建并运行新nginx容器，挂载本地目录

docker run -d \
--name seata \
--restart=always \
-p 8099:8099 \
-p 7099:7099 \
-e SEATA_IP=192.168.119.244 \
-v /usr/local/docker_data/seata:/seata-server/resources \
--privileged=true \
--network my-net \
seataio/seata-server:1.5.2

• d: 使容器在后台以守护进程模式运行。
• -name seata: 为新创建的容器指定一个名称，这里是seata。
• p 8099:8099: 将宿主机的8099端口映射到容器的8099端口。
• p 7099:7099: 将宿主机的7099端口映射到容器的7099端口。
• e SEATA_IP=192.168.119.244: 设置环境变量SEATA_IP，用于指定 Seata 服务器的 IP 地址。这通常用于告诉Seata服务器它的IP地址是什么，以便其他服务或客户端可以正确地连接到它。
• v /usr/local/docker_data/seata:/seata-server/resources:将宿主机的/usr/local/docker_data/seata目录挂载到容器内的/seata-server/resources目录。这样，你可以在宿主机上修改Seata的配置文件或其他资源，并立即在容器中看到这些更改。
• -privileged=true: 给予容器额外的权限。通常，这个选项应该谨慎使用，因为它允许容器几乎可以执行宿主机上的任何操作。但在某些情况下，例如需要访问宿主机硬件或执行某些需要特权才能进行的操作时，这可能是必要的。
• -network my-net: 将容器连接到名为my-net的自定义Docker网络。这允许你控制容器之间的网络连接和隔离。
• seataio/seata-server:1.5.2: 这是你想要基于的Docker镜像的名称和标签。Docker会从它的镜像仓库（如Docker Hub）中拉取这个版本的Seata服务器镜像，并基于这个镜像创建和运行容器。

3. 数据库文件

CREATE DATABASE IF NOT EXISTS `seata`;
USE `seata`;

CREATE TABLE IF NOT EXISTS `global_table`
(
    `xid`                       VARCHAR(128) NOT NULL,
    `transaction_id`            BIGINT,
    `status`                    TINYINT      NOT NULL,
    `application_id`            VARCHAR(32),
    `transaction_service_group` VARCHAR(32),
    `transaction_name`          VARCHAR(128),
    `timeout`                   INT,
    `begin_time`                BIGINT,
    `application_data`          VARCHAR(2000),
    `gmt_create`                DATETIME,
    `gmt_modified`              DATETIME,
    PRIMARY KEY (`xid`),
    KEY `idx_status_gmt_modified` (`status` , `gmt_modified`),
    KEY `idx_transaction_id` (`transaction_id`)
) ENGINE = InnoDB
  DEFAULT CHARSET = utf8mb4;

CREATE TABLE IF NOT EXISTS `branch_table`
(
    `branch_id`         BIGINT       NOT NULL,
    `xid`               VARCHAR(128) NOT NULL,
    `transaction_id`    BIGINT,
    `resource_group_id` VARCHAR(32),
    `resource_id`       VARCHAR(256),
    `branch_type`       VARCHAR(8),
    `status`            TINYINT,
    `client_id`         VARCHAR(64),
    `application_data`  VARCHAR(2000),
    `gmt_create`        DATETIME(6),
    `gmt_modified`      DATETIME(6),
    PRIMARY KEY (`branch_id`),
    KEY `idx_xid` (`xid`)
) ENGINE = InnoDB
  DEFAULT CHARSET = utf8mb4;

CREATE TABLE IF NOT EXISTS `lock_table`
(
    `row_key`        VARCHAR(128) NOT NULL,
    `xid`            VARCHAR(128),
    `transaction_id` BIGINT,
    `branch_id`      BIGINT       NOT NULL,
    `resource_id`    VARCHAR(256),
    `table_name`     VARCHAR(32),
    `pk`             VARCHAR(36),
    `status`         TINYINT      NOT NULL DEFAULT '0' COMMENT '0:locked ,1:rollbacking',
    `gmt_create`     DATETIME,
    `gmt_modified`   DATETIME,
    PRIMARY KEY (`row_key`),
    KEY `idx_status` (`status`),
    KEY `idx_branch_id` (`branch_id`),
    KEY `idx_xid_and_branch_id` (`xid` , `branch_id`)
) ENGINE = InnoDB
  DEFAULT CHARSET = utf8mb4;

CREATE TABLE IF NOT EXISTS `distributed_lock`
(
    `lock_key`       CHAR(20) NOT NULL,
    `lock_value`     VARCHAR(20) NOT NULL,
    `expire`         BIGINT,
    primary key (`lock_key`)
) ENGINE = InnoDB
  DEFAULT CHARSET = utf8mb4;

INSERT INTO `distributed_lock` (lock_key, lock_value, expire) VALUES ('AsyncCommitting', ' ', 0);
INSERT INTO `distributed_lock` (lock_key, lock_value, expire) VALUES ('RetryCommitting', ' ', 0);
INSERT INTO `distributed_lock` (lock_key, lock_value, expire) VALUES ('RetryRollbacking', ' ', 0);
INSERT INTO `distributed_lock` (lock_key, lock_value, expire) VALUES ('TxTimeoutCheck', ' ', 0);

-- for AT mode you must to init this sql for you business database. the seata server not need it.
-- 对于AT模式，您必须为您的业务数据库初始化此SQL。SEATA服务不需要它。
CREATE TABLE IF NOT EXISTS `undo_log`
(
    `branch_id`     BIGINT       NOT NULL COMMENT 'branch transaction id',
    `xid`           VARCHAR(128) NOT NULL COMMENT 'global transaction id',
    `context`       VARCHAR(128) NOT NULL COMMENT 'undo_log context,such as serialization',
    `rollback_info` LONGBLOB     NOT NULL COMMENT 'rollback info',
    `log_status`    INT(11)      NOT NULL COMMENT '0:normal status,1:defense status',
    `log_created`   DATETIME(6)  NOT NULL COMMENT 'create datetime',
    `log_modified`  DATETIME(6)  NOT NULL COMMENT 'modify datetime',
    UNIQUE KEY `ux_undo_log` (`xid`, `branch_id`)
) ENGINE = InnoDB
  AUTO_INCREMENT = 1
  DEFAULT CHARSET = utf8mb4 COMMENT ='AT transaction mode undo table';

1.1.5 部署 RabbitMQ（消息队列）

1. 简易安装

docker run -d \
 --name mq \
 --restart=always \
 -e RABBITMQ_DEFAULT_USER=root \
 -e RABBITMQ_DEFAULT_PASS=123321 \
 -p 15672:15672 \
 -p 5672:5672 \
 rabbitmq:3.8-management

2. 自定义安装

docker run -d \
 --name mq \
 --restart=always \
 -e RABBITMQ_DEFAULT_USER=root \
 -e RABBITMQ_DEFAULT_PASS=123321 \
 -v mq-plugins:/plugins \
 --hostname mq \
 -p 15672:15672 \
 -p 5672:5672 \
 --network my-net\
 rabbitmq:3.8-management

1. docker run: 基于指定的镜像创建一个新的容器并运行它。
2. -d: 在后台运行容器，并返回容器ID。
3. -e: 设置环境变量。这里设置了RabbitMQ的默认用户名和密码。
4. -v mq-plugins:/plugins: 将主机上的 mq-plugins 卷（如果它存在）挂载到容器内的 /plugins 目录。如果不存在，Docker会自动创建它。这通常用于添加或覆盖RabbitMQ的插件。
5. –name mq: 为容器指定一个名称，这里是 mq。
6. –hostname mq: 设置容器的主机名为 mq（可选）。
7. -p 15672:15672: 将容器的15672端口映射到主机的15672端口。这是RabbitMQ的管理界面端口。
8. -p 5672:5672: 将容器的5672端口映射到主机的5672端口。这是RabbitMQ的AMQP协议端口。
9. –network my-net: 将容器连接到名为 my-net 的Docker网络（可选）。
10. rabbitmq:3.8-management: 指定要运行的Docker镜像，这里是RabbitMQ 3.8版本的管理镜像。

1.1.6 部署 Elasticsearch

1. 简易安装

docker run -d \
  --name es \
  --restart=always \
  -e "discovery.type=single-node" \
  -p 9200:9200 \
  -p 9300:9300 \
  elasticsearch:7.12.1

2. 自定义安装

docker run -d \
  --name es \
  --restart=always \
  -e "ES_JAVA_OPTS=-Xms512m -Xmx512m" \
  -e "discovery.type=single-node" \
  -v es-data:/usr/share/elasticsearch/data \
  -v es-plugins:/usr/share/elasticsearch/plugins \
  --privileged \
  --network my-net \
  -p 9200:9200 \
  -p 9300:9300 \
  elasticsearch:7.12.1

• d: 在后台运行容器（即“分离”模式）。
• -name es: 为容器指定一个名称，这里是 es。
• e “ES_JAVA_OPTS=-Xms512m -Xmx512m”: 设置环境变量来指定 Elasticsearch 的 Java 虚拟机堆大小初始值（Xms）和最大值（Xmx），都设置为 512MB。
• e “discovery.type=single-node”: 在单节点模式下运行 Elasticsearch。如果打算运行 Elasticsearch 集群，这个参数就不是必要的。但在单节点设置下，它是必要的**。**
• v es-data:/usr/share/elasticsearch/data: 创建一个名为 es-data 的 Docker 卷（如果它还不存在），并将其挂载到容器内的 /usr/share/elasticsearch/data 目录。这是 Elasticsearch 存储其索引数据的地方。
• v es-plugins:/usr/share/elasticsearch/plugins: 创建一个名为 es-plugins 的 Docker 卷（如果它还不存在），并将其挂载到容器内的 /usr/share/elasticsearch/plugins 目录。这是 Elasticsearch 插件的安装位置。
• -privileged: 以特权模式运行容器。这通常不推荐，因为它会赋予容器更多的权限，可能带来安全风险。但在某些情况下，特别是当需要访问宿主机上的设备或执行某些需要更高权限的操作时，可能需要这样做。
• -network my-net: 将容器连接到名为 my-net 的 Docker 网络。
• p 9200:9200: 将容器的 9200 端口映射到宿主机的 9200 端口。这是 Elasticsearch 的 HTTP API 端口。
• p 9300:9300: 将容器的 9300 端口映射到宿主机的 9300 端口。这是 Elasticsearch 的传输层端口，用于节点之间的通信。
• elasticsearch:7.12.1: 指定要运行的 Docker 镜像，这里是 Elasticsearch 7.12.1 版本。

1.1.7 部署 Kibana（分析与可视化平台）

Kibana是一个开源的分析与可视化平台，设计出来用于和Elasticsearch一起使用的。

1. 简易安装

docker run -d \
--name kibana \
-e ELASTICSEARCH_HOSTS=http://es:9200 \
-p 5601:5601  \
kibana:7.12.1

2. 自定义安装

docker run -d \
--name kibana \
--restart=always \
-e ELASTICSEARCH_HOSTS=http://es:9200 \
-p 5601:5601  \
--network my-net \
kibana:7.12.1

1. d: 使容器在后台运行（detached mode）。这是必要的，除非你希望在前台手动管理容器。
2. -name kibana: 为容器指定一个名称。虽然这不是严格必要的（Docker 会自动生成一个名称），但为容器指定一个有意义且易于记忆的名称通常是很好的做法。
3. -restart=always: 设置容器的重启策略为始终重启。这取决于你的需求。如果你希望容器在退出时始终自动重启，那么这个参数是必要的。但如果你在某些情况下不希望容器重启，那么这个参数就不是必要的。
4. e ELASTICSEARCH_HOSTS=http://es:9200: 设置 Kibana 的环境变量，告诉它 Elasticsearch 的地址。这是必要的，因为 Kibana 需要知道如何连接到 Elasticsearch 实例。注意这里假设你有一个名为 es 的容器或服务在 hm-net 网络中运行，并且监听 9200 端口。
5. -network=hm-net: 将容器连接到名为 hm-net 的自定义网络。这取决于你的网络配置和需求。如果你希望容器使用默认的 bridge 网络或 host 网络，或者你已经确保了 Kibana 容器可以通过其他方式访问 Elasticsearch（例如，通过 Docker Compose 的服务发现），那么这个参数就不是必要的。
6. p 5601:5601: 映射容器的 5601 端口到宿主机的 5601 端口。这是必要的，除非你有特定的路由设置，或者打算使用其他方式访问 Kibana。

💡 配置文件必须在运行容器前完成创建和配置，否则无法使其生效