要做本文章中的实现，会docker技术是前提，这里默认你已经会了，下面开始正文：
1、先在dockerHub上拉取redis镜像，我们就以最新的版本为例拉取：
docker pull redis
2、由于docker容器中的redis是没有redis.conf的，所以我们是自己在本地写个配置文件，并将其挂载到docker容器内部。redis.conf的配置内容可以去官网上复制，咱们共用一个ip，分6379(master),6380(slave),6381(slave)，这里献上自己简单的配置内容：
# Redis配置文件样例
# Note on units: when memory size is needed, it is possible to specifiy
# 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.
# Redis默认不是以守护进程的方式运行，可以通过该配置项修改，使用yes启用守护进程
# 启用守护进程后，Redis会把pid写到一个pidfile中，在/var/run/redis.pid
daemonize no
# 当Redis以守护进程方式运行时，Redis默认会把pid写入/var/run/redis.pid文件，可以通过pidfile指定
pidfile /var/run/redis.pid
# 指定Redis监听端口，默认端口为6379
# 如果指定0端口，表示Redis不监听TCP连接
port 6379
# 绑定的主机地址
# 你可以绑定单一接口，如果没有绑定，所有接口都会监听到来的连接
# bind 127.0.0.1
# Specify the path for the unix socket that will be used to listen for
# incoming connections. There is no default, so Redis will not listen
# on a unix socket when not specified.
#
# unixsocket /tmp/redis.sock
# unixsocketperm 755
# 当客户端闲置多长时间后关闭连接，如果指定为0，表示关闭该功能
timeout 0
# 指定日志记录级别，Redis总共支持四个级别：debug、verbose、notice、warning，默认为verbose
# debug (很多信息, 对开发／测试比较有用)
# 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 verbose
# 日志记录方式，默认为标准输出，如果配置为redis为守护进程方式运行，而这里又配置为标准输出，则日志将会发送给/dev/null
logfile stdout
# 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
# 设置数据库的数量，默认数据库为0，可以使用select <dbid>命令在连接上指定数据库id
# dbid是从0到‘databases’-1的数目
databases 16
################################ SNAPSHOTTING #################################
# 指定在多长时间内，有多少次更新操作，就将数据同步到数据文件，可以多个条件配合
# Save the DB on disk:
#
# save <seconds> <changes>
#
# Will save the DB if both the given number of seconds and the given
# number of write operations against the DB occurred.
#
# 满足以下条件将会同步数据:
# 900秒（15分钟）内有1个更改
# 300秒（5分钟）内有10个更改
# 60秒内有10000个更改
# Note: 可以把所有“save”行注释掉，这样就取消同步操作了
save 900 1
save 300 10
save 60 10000
# 指定存储至本地数据库时是否压缩数据，默认为yes，Redis采用LZF压缩，如果为了节省CPU时间，可以关闭该选项，但会导致数据库文件变的巨大
rdbcompression yes
# 指定本地数据库文件名，默认值为dump.rdb
dbfilename dump.rdb
# 工作目录.
# 指定本地数据库存放目录，文件名由上一个dbfilename配置项指定
#
# Also the Append Only File will be created inside this directory.
#
# 注意，这里只能指定一个目录，不能指定文件名
dir ./
################################# REPLICATION #################################
# 主从复制。使用slaveof从 Redis服务器复制一个Redis实例。注意，该配置仅限于当前slave有效
# so for example it is possible to configure the slave to save the DB with a
# different interval, or to listen to another port, and so on.
# 设置当本机为slav服务时，设置master服务的ip地址及端口，在Redis启动时，它会自动从master进行数据同步
# 注意：这里的ip写自己的ip地址 主节点注释，从节点放开。
# slaveof 10.100.58.177 6379
# 当master服务设置了密码保护时，slav服务连接master的密码
# 下文的“requirepass”配置项可以指定密码
# masterauth <master-password>
# When a slave lost the connection with the master, or when the replication
# is still in progress, the slave can act in two different ways:
#
# 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
# still reply to client requests, possibly with out of data data, or the
# data set may just be empty if this is the first synchronization.
#
# 2) if slave-serve-stale data is set to 'no' the slave will reply with
# an error "SYNC with master in progress" to all the kind of commands
# but to INFO and SLAVEOF.
#
slave-serve-stale-data yes
# Slaves send PINGs to server in a predefined interval. It's possible to change
# this interval with the repl_ping_slave_period option. The default value is 10
# seconds.
#
# repl-ping-slave-period 10
# The following option sets a timeout for both Bulk transfer I/O timeout and
# master data or ping response timeout. The default value is 60 seconds.
#
# It is important to make sure that this value is greater than the value
# specified for repl-ping-slave-period otherwise a timeout will be detected
# every time there is low traffic between the master and the slave.
#
# repl-timeout 60
################################## SECURITY ###################################
# Warning: since Redis is pretty fast an outside user can try up to
# 150k passwords per second against a good box. This means that you should
# use a very strong password otherwise it will be very easy to break.
# 设置Redis连接密码，如果配置了连接密码，客户端在连接Redis时需要通过auth <password>命令提供密码，默认关闭
# requirepass foobared
# Command renaming.
#
# It is possilbe to change the name of dangerous commands in a shared
# environment. For instance the CONFIG command may be renamed into something
# of hard to guess so that it will be still available for internal-use
# tools but not available for general clients.
#
# Example:
#
# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
#
# It is also possilbe to completely kill a command renaming it into
# an empty string:
#
# rename-command CONFIG ""
################################### LIMITS ####################################
# 设置同一时间最大客户端连接数，默认无限制，Redis可以同时打开的客户端连接数为Redis进程可以打开的最大文件描述符数，
# 如果设置maxclients 0，表示不作限制。当客户端连接数到达限制时，Redis会关闭新的连接并向客户端返回max Number of clients reached错误信息
# maxclients 128
# Don't use more memory than the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys with an
# EXPIRE set. It will try to start freeing keys that are going to expire
# in little time and preserve keys with a longer time to live.
# Redis will also try to remove objects from free lists if possible.
#
# If all this fails, Redis will start to reply with errors to commands
# that will use more memory, like SET, LPUSH, and so on, and will continue
# to reply to most read-only commands like GET.
#
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
# 'state' server or cache, not as a real DB. When Redis is used as a real
# database the memory usage will grow over the weeks, it will be obvious if
# it is going to use too much memory in the long run, and you'll have the time
# to upgrade. With maxmemory after the limit is reached you'll start to get
# errors for write operations, and this may even lead to DB inconsistency.
# 指定Redis最大内存限制，Redis在启动时会把数据加载到内存中，达到最大内存后，Redis会先尝试清除已到期或即将到期的Key，
# 当此方法处理后，仍然到达最大内存设置，将无法再进行写入操作，但仍然可以进行读取操作。
# Redis新的vm机制，会把Key存放内存，Value会存放在swap区
# maxmemory <bytes>
# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
# is reached? You can select among five behavior:
#
# volatile-lru -> remove the key with an expire set using an LRU algorithm
# allkeys-lru -> remove any key accordingly to the LRU algorithm
# volatile-random -> remove a random key with an expire set
# allkeys->random -> remove a random key, any key
# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
# noeviction -> don't expire at all, just return an error on write operations
#
# Note: with all the kind of policies, Redis will return an error on write
# operations, when there are not suitable keys for eviction.
#
# At the date of writing this commands are: set setnx setex append
# incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
# sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
# zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
# getset mset msetnx exec sort
#
# The default is:
#
# maxmemory-policy volatile-lru
# LRU and minimal TTL algorithms are not precise algorithms but approximated
# algorithms (in order to save memory), so you can select as well the sample
# size to check. For instance for default Redis will check three keys and
# pick the one that was used less recently, you can change the sample size
# using the following configuration directive.
#
# maxmemory-samples 3
############################## APPEND ONLY MODE ###############################
#
# Note that you can have both the async dumps and the append only file if you
# like (you have to comment the "save" statements above to disable the dumps).
# Still if append only mode is enabled Redis will load the data from the
# log file at startup ignoring the dump.rdb file.
# 指定是否在每次更新操作后进行日志记录，Redis在默认情况下是异步的把数据写入磁盘，如果不开启，可能会在断电时导致一段时间内的数据丢失。
# 因为redis本身同步数据文件是按上面save条件来同步的，所以有的数据会在一段时间内只存在于内存中。默认为no
# IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
# log file in background when it gets too big.
appendonly yes
# 指定更新日志文件名，默认为appendonly.aof
# appendfilename appendonly.aof
# The fsync() call tells the Operating System to actually write data on disk
# instead to wait 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.
# 指定更新日志条件，共有3个可选值：
# no:表示等操作系统进行数据缓存同步到磁盘（快）
# always:表示每次更新操作后手动调用fsync()将数据写到磁盘（慢，安全）
# everysec:表示每秒同步一次（折衷，默认值）
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", that in pratical terms means that it is
# possible to lost 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 will growth by the specified percentage.
#
# This is how it works: Redis remembers the size of the AOF file after the
# latest rewrite (or if no rewrite 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 precentage of zero in order to disable the automatic AOF
# rewrite feature.
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
################################## 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 1024
注意：port 6379 --端口号
slaveof 10.100.58.177 6379 --设置主节点的ip和端口号
appendonly yes --开启 redis 的 aof 持久化机制
上面是6379的配置内容，6380和6381的配置只需要更改port为对应的端口号即可。
目录结构如下：
huipanxing@huipanxing-OptiPlex-7050:/opt/redis$ ll
总用量 20
drwxrwxr-x 5 huipanxing huipanxing 4096 8月 29 16:20 ./
drwxr-xr-x 22 huipanxing huipanxing 4096 8月 29 15:52 ../
drwxr-xr-x 3 root root 4096 8月 30 15:18 redis6379/
drwxr-xr-x 3 root root 4096 8月 30 15:19 redis6380/
drwxr-xr-x 3 root root 4096 8月 30 15:20 redis6381/
huipanxing@huipanxing-OptiPlex-7050:/opt/redis/redis6379$ ll
总用量 36
drwxr-xr-x 3 root root 4096 8月 30 15:18 ./
drwxrwxr-x 5 huipanxing huipanxing 4096 8月 29 16:20 ../
drwxr-xr-x 2 guest-czbjd5 root 4096 8月 30 15:47 data/
-rw-r--r-- 1 root root 14174 8月 30 11:00 redis.conf
-rw------- 1 root root 4096 8月 30 11:00 .re.swp
-rw-r--r-- 1 root root 730 8月 30 15:32 sentinel.conf
3、启动三个redis容器实例：
docker run -d -p 6379:6379 -v /opt/redis/redis6379/redis.conf:/etc/redis/redis.conf -v /opt/redis/redis6379/data:/data [镜像ID] redis-server /etc/redis/redis.conf
注意：镜像ID可以用到docker images命令获取
-p 6379:6379 --启动对外暴露端口
-v /opt/redis/redis6379/redis.conf:/etc/redis/redis.conf --本地的redis配置与容器内部的配置挂载
-v /opt/redis/redis6379/data:/data --本地的redis的数据文件夹与容器内部的数据文件挂载，里面可以存持久化文件等等
docker run -d -p 6380:6380 -v /opt/redis/redis6380/redis.conf:/etc/redis/redis.conf -v /opt/redis/redis6380/data:/data [镜像ID] redis-server /etc/redis/redis.conf
docker run -d -p 6381:6381 -v /opt/redis/redis6381/redis.conf:/etc/redis/redis.conf -v /opt/redis/redis6381/data:/data [镜像ID] redis-server /etc/redis/redis.conf
4、编写哨兵模式用的sentinel.conf文件，内容为：
port 26379
dir "/data"
logfile "sentinel-26379.log"
sentinel monitor mymaster 10.100.58.177 6379 1
sentinel down-after-milliseconds mymaster 10000
sentinel failover-timeout mymaster 60000
注意：sentinel down-after-milliseconds mymaster 10000 --心跳检测时间，可以设置小点
port 26380
dir "/data"
logfile "sentinel-26380.log"
sentinel monitor mymaster 10.100.58.177 6379 1
sentinel down-after-milliseconds mymaster 10000
sentinel failover-timeout mymaster 60000
port 26381
dir "/data"
logfile "sentinel-26381.log"
sentinel monitor mymaster 10.100.58.177 6379 1
sentinel down-after-milliseconds mymaster 10000
sentinel failover-timeout mymaster 60000
6、启动哨兵的容器实例：
docker run -d -p 26379:26379 -v /opt/redis/redis6379/sentinel.conf:/etc/redis/sentinel.conf -v /opt/redis/redis6379/data:/data [镜像ID] redis-sentinel /etc/redis/sentinel.conf
注意：镜像ID可以用到docker images命令获取
-p 6379:6379 --启动对外暴露端口
-v /opt/redis/redis6379/sentinel.conf:/etc/redis/sentinel.conf --本地的redis哨兵配置与容器内部的哨兵配置挂载
-v /opt/redis/redis6379/data:/data --本地的redis的数据文件夹与容器内部的数据文件挂载，里面可以存持久化文件等等
docker run -d -p 26380:26380 -v /opt/redis/redis6380/sentinel.conf:/etc/redis/sentinel.conf -v /opt/redis/redis6380/data:/data [镜像ID] redis-sentinel /etc/redis/sentinel.conf
docker run -d -p 26381:26381 -v /opt/redis/redis6381/sentinel.conf:/etc/redis/sentinel.conf -v /opt/redis/redis6381/data:/data [镜像ID] redis-sentinel /etc/redis/sentinel.conf
启动完成的样子：
root@huipanxing-OptiPlex-7050:/opt/redis/redis6379# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
7c33aad349db f7302e4ab3a8 "docker-entrypoint.s…" 5 seconds ago Up 3 seconds 6379/tcp, 0.0.0.0:26381->26381/tcp ecstatic_shirley
264f878780ca f7302e4ab3a8 "docker-entrypoint.s…" 9 seconds ago Up 7 seconds 6379/tcp, 0.0.0.0:26380->26380/tcp frosty_ride
0b657d83a664 f7302e4ab3a8 "docker-entrypoint.s…" 14 seconds ago Up 12 seconds 6379/tcp, 0.0.0.0:26379->26379/tcp brave_darwin
68ac19cb5055 f7302e4ab3a8 "docker-entrypoint.s…" 34 seconds ago Up 32 seconds 6379/tcp, 0.0.0.0:6381->6381/tcp sleepy_pasteur
d6192433aaf3 f7302e4ab3a8 "docker-entrypoint.s…" 38 seconds ago Up 36 seconds 6379/tcp, 0.0.0.0:6380->6380/tcp ecstatic_feynman
a75c20c76006 f7302e4ab3a8 "docker-entrypoint.s…" 2 minutes ago Up 2 minutes 0.0.0.0:6379->6379/tcp gallant_poincare
7、测试主从复制
127.0.0.1:6379> info replication
# Replication
role:master
connected_slaves:2
slave0:ip=172.17.0.1,port=6380,state=online,offset=22161,lag=1
slave1:ip=172.17.0.1,port=6381,state=online,offset=22161,lag=1
master_replid:61b6ced70d298f4f940aba6e658fc258067fccfb
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:22299
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:22299
127.0.0.1:6380> info replication
# Replication
role:slave
master_host:10.100.58.177
master_port:6379
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:36335
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:61b6ced70d298f4f940aba6e658fc258067fccfb
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:36335
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:36335
127.0.0.1:6381> info replication
# Replication
role:slave
master_host:10.100.58.177
master_port:6379
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:19663
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:61b6ced70d298f4f940aba6e658fc258067fccfb
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:19663
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:15
repl_backlog_histlen:19649
此时，6379主节点可以写，可以读，6380和6381只可以读，并且已经实现主从复制功能。
8、测试哨兵模式功能
停止掉6379主节点，查看6380和6381的节点信息：
root@huipanxing-OptiPlex-7050:/opt/redis/redis6379# docker stop a75c20c76006
a75c20c76006
127.0.0.1:6380> info replication
# Replication
role:master
connected_slaves:1
slave0:ip=172.17.0.1,port=6381,state=online,offset=107561,lag=1
master_replid:cff6e45a272fdf3a58165f92a4f4e35c139b460c
master_replid2:61b6ced70d298f4f940aba6e658fc258067fccfb
master_repl_offset:107696
second_repl_offset:78858
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:107696
127.0.0.1:6381> info replication
# Replication
role:slave
master_host:172.17.0.1
master_port:6380
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:115312
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:cff6e45a272fdf3a58165f92a4f4e35c139b460c
master_replid2:61b6ced70d298f4f940aba6e658fc258067fccfb
master_repl_offset:115312
second_repl_offset:78858
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:15
repl_backlog_histlen:115298
到这里，用docker已经实现了redis的主从复制+读写分离+哨兵模式
149
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
