Redis 哨兵模式安装方法

哨兵模式参数
https://blog.csdn.net/wtyvhreal/article/details/45743985
https://www.cnblogs.com/zhoujinyi/p/6430116.html

安装SSH服务
sudo apt-get install openssh-server
sudo service ssh start　
====================================================================
DHCP设置
/etc/network/interfaces

#The primary network interface - use DHCP to find our address
auto eth0
iface eth0 inet dhcp

sudo /etc/init.d/networking restart
静态IP设置
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.2.1
gateway 192.168.2.254
netmask 255.255.255.0
#network 192.168.2.0
#broadcast 192.168.2.255
====================================================================
ubuntu 离线安装

一在一台能联网的机器上制作安装包
1 sudo apt-get install （-d 只下载不安装）

2 全部安装完成后拷贝到debs文件夹
cp -r /var/cache/apt/archives/* /var/debs/

3创建Packages并更改文件夹权限
touch /var/debs/Packages.gz
chmod -R 777 /var/debs/ # 这一步是为了获得文件的可写可读可执行权限，要不然后面会失败

4创建索引
dpkg-scanpackages ./debs /dev/null | gzip > /var/debs/Packages.gz# 创建索引

dpkg-scanpackages若未安装
sudo apt-get install dpkg-dev

二在不能联网的机器上进行安装

1 将debs文件夹拷贝到/var目录下

2 修改source.list文件
vi /etc/apt/sources.list
将sources.list 原来的内容都注释掉。在最后添加
deb file:/var debs/

3 apt-get更新
apt-get update

4 使用apt-get 正常安装

==================================================================
redis 安装

1 分别将redis-3.2.11.tar.gz上传到 /usr/local/src

2 解压
tar -zxvf redis-3.2.11.tar.gz

3创建redis安装目录和配置文件目录
mkdir -p /usr/local/redis
mkdir -p /usr/local/redis/conf

4 make&&install
cd /usr/local/src/redis-3.2.11/src
make
make PREFIX=/usr/local/redis install
------如果没有安装gcc和make------
apt-get install make
apt-get install gcc
---------------------------------

5修改配置文件
redis.conf
master
bind 127.0.0.1 ==> #bind 127.0.0.1
protected-mode yes ==>protected-mode no
logfile ""==>logfile "/usr/local/redis/conf/redis.log"
slave-read-only yes ==>slave-read-only no

slave
slaveof <masterip> <masterport> ==> slaveof 192.168.0.10 6379

6 启动redis 主从模式并测试
sh redis_init_script start&
测试
./redis-cli -h 192.168.0.10 -p 6379

7修改sentinel配置文件
#protected-mode no ==》protected-mode no

sentinel monitor mymaster 127.0.0.1 6379 2 ==》
sentinel monitor mymaster 192.168.0.10 6379 2

sentinel down-after-milliseconds mymaster 30000 ==>
sentinel down-after-milliseconds mymaster 5000

sentinel failover-timeout mymaster 180000 ==>
sentinel failover-timeout mymaster 30000

8 启动哨兵
./redis-sentinel /usr/local/redis/conf/sentinel.conf &

9 测试，停止master
sh redis_init_script stop &

10 出现以下日志

master

1747:X 15 Apr 22:21:20.494 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1747:X 15 Apr 22:21:20.619 # Sentinel ID is 061b12654feee1e98d0b5a96177f69b35da737aa
1747:X 15 Apr 22:21:20.619 # +monitor master mymaster 192.168.0.10 6379 quorum 2
1747:X 15 Apr 22:21:20.621 * +slave slave 192.168.0.12:6379 192.168.0.12 6379 @ mymaster 192.168.0.10 6379
1747:X 15 Apr 22:21:20.639 * +slave slave 192.168.0.11:6379 192.168.0.11 6379 @ mymaster 192.168.0.10 6379
1747:X 15 Apr 22:21:22.520 * +sentinel sentinel 33a5abbf8412c85dd6922ddae45f417cb58c1a3e 192.168.0.11 26379 @ mymaster 192.168.0.10 6379
1747:X 15 Apr 22:21:22.535 * +sentinel sentinel 4b918ab826fa0fd71ed74f5d2bfd6ae0d88d76ac 192.168.0.12 26379 @ mymaster 192.168.0.10 6379
1747:X 15 Apr 22:24:50.496 # +sdown master mymaster 192.168.0.10 6379
1747:X 15 Apr 22:24:50.606 # +odown master mymaster 192.168.0.10 6379 #quorum 2/2
1747:X 15 Apr 22:24:50.606 # +new-epoch 1
1747:X 15 Apr 22:24:50.607 # +try-failover master mymaster 192.168.0.10 6379
1747:X 15 Apr 22:24:50.612 # +vote-for-leader 061b12654feee1e98d0b5a96177f69b35da737aa 1
1747:X 15 Apr 22:24:50.633 # 4b918ab826fa0fd71ed74f5d2bfd6ae0d88d76ac voted for 061b12654feee1e98d0b5a96177f69b35da737aa 1
1747:X 15 Apr 22:24:50.664 # 33a5abbf8412c85dd6922ddae45f417cb58c1a3e voted for 061b12654feee1e98d0b5a96177f69b35da737aa 1
1747:X 15 Apr 22:24:50.679 # +elected-leader master mymaster 192.168.0.10 6379
1747:X 15 Apr 22:24:50.680 # +failover-state-select-slave master mymaster 192.168.0.10 6379
1747:X 15 Apr 22:24:50.734 # +selected-slave slave 192.168.0.11:6379 192.168.0.11 6379 @ mymaster 192.168.0.10 6379
1747:X 15 Apr 22:24:50.734 * +failover-state-send-slaveof-noone slave 192.168.0.11:6379 192.168.0.11 6379 @ mymaster 192.168.0.10 6379
1747:X 15 Apr 22:24:50.792 * +failover-state-wait-promotion slave 192.168.0.11:6379 192.168.0.11 6379 @ mymaster 192.168.0.10 6379
1747:X 15 Apr 22:24:51.704 # +promoted-slave slave 192.168.0.11:6379 192.168.0.11 6379 @ mymaster 192.168.0.10 6379
1747:X 15 Apr 22:24:51.704 # +failover-state-reconf-slaves master mymaster 192.168.0.10 6379
1747:X 15 Apr 22:24:51.770 * +slave-reconf-sent slave 192.168.0.12:6379 192.168.0.12 6379 @ mymaster 192.168.0.10 6379

slave
1507:X 15 Apr 22:21:20.503 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1507:X 15 Apr 22:21:20.653 # Sentinel ID is 33a5abbf8412c85dd6922ddae45f417cb58c1a3e
1507:X 15 Apr 22:21:20.653 # +monitor master mymaster 192.168.0.10 6379 quorum 2
1507:X 15 Apr 22:21:20.656 * +slave slave 192.168.0.12:6379 192.168.0.12 6379 @ mymaster 192.168.0.10 6379
1507:X 15 Apr 22:21:20.663 * +slave slave 192.168.0.11:6379 192.168.0.11 6379 @ mymaster 192.168.0.10 6379
1507:X 15 Apr 22:21:22.534 * +sentinel sentinel 4b918ab826fa0fd71ed74f5d2bfd6ae0d88d76ac 192.168.0.12 26379 @ mymaster 192.168.0.10 6379
1507:X 15 Apr 22:21:22.566 * +sentinel sentinel 061b12654feee1e98d0b5a96177f69b35da737aa 192.168.0.10 26379 @ mymaster 192.168.0.10 6379
1507:X 15 Apr 22:24:50.593 # +sdown master mymaster 192.168.0.10 6379
1507:X 15 Apr 22:24:50.624 # +new-epoch 1
1507:X 15 Apr 22:24:50.662 # +vote-for-leader 061b12654feee1e98d0b5a96177f69b35da737aa 1
1507:X 15 Apr 22:24:50.675 # +odown master mymaster 192.168.0.10 6379 #quorum 3/2
1507:X 15 Apr 22:24:50.676 # Next failover delay: I will not start a failover before Sun Apr 15 22:25:51 2018
1507:X 15 Apr 22:24:51.770 # +config-update-from sentinel 061b12654feee1e98d0b5a96177f69b35da737aa 192.168.0.10 26379 @ mymaster 192.168.0.10 6379
1507:X 15 Apr 22:24:51.771 # +switch-master mymaster 192.168.0.10 6379 192.168.0.11 6379
1507:X 15 Apr 22:24:51.773 * +slave slave 192.168.0.12:6379 192.168.0.12 6379 @ mymaster 192.168.0.11 6379
1507:X 15 Apr 22:24:51.774 * +slave slave 192.168.0.10:6379 192.168.0.10 6379 @ mymaster 192.168.0.11 6379
1507:X 15 Apr 22:24:56.802 # +sdown slave 192.168.0.10:6379 192.168.0.10 6379 @ mymaster 192.168.0.11 6379

Redis 哨兵模式安装方法相关推荐

redis哨兵模式没有切换主机_Redis哨兵（Sentinel）模式
Redis哨兵(Sentinel)模式在这里插入图片描述一.主从复制高可用当我们使用主从复制出现的问题手动故障转移写能力和存储能力受限主从复制 -master 宕机故障处理主从切换技术的 ...
Redis哨兵模式搭建
主从切换技术的方法是:当主服务器宕机后,需要手动把一台从服务器切换为主服务器,这就需要人工干预,费事费力,还会造成一段时间内服务不可用.这不是一种推荐的方式,更多时候,我们优先考虑哨兵模式一:哨兵模 ...
Redis哨兵模式及集群
一.redis哨兵模式哨兵的核心功能:在主从复制的基础上,哨兵引入了主节点的自动故障转移 1.哨兵模式的原理哨兵(sentinel):是一个分布式系统,用于对主从结构中的每台服务器进行监控,当出现 ...
【NOSQL】redis哨兵模式、集群搭建
目录一.redis高可用一.Redis主从复制 1.1主从复制的作用 1.2主从复制流程二.搭建Rdeis主从复制 2.1安装redis 2.1.1环境准备 2.1.2安装redis 2.1.3 ...
Redis——Redis哨兵模式
Redis哨兵模式 Redis哨兵模式概述哨兵的作用启用哨兵模式配置单哨兵配置单哨兵启动单哨兵配置集群哨兵配置集群哨兵启动集群哨兵哨兵模式的全部配置 Redis哨兵模式概述主从切换 ...
Redis主从复制、Redis哨兵模式、Redis集群
目录 Redis主从复制主从复制 Redis哨兵模式哨兵sentinel 哨兵的工作原理哨兵sentinel-实现高可用 sentinel的坑修改从节点的选举优先级 sentinel.conf ...
使用bitnamiredis-sentinel部署Redis 哨兵模式
使用bitnami/redis-sentinel部署Redis 哨兵模式为什么使用 Bitnami 镜像? Bitnami 密切跟踪上游源代码更改,并使用我们的自动化系统及时发布此镜像的新版本. 借 ...
Redis 哨兵模式原理
主从切换技术的方法是:当主服务器宕机后,需要手动把一台从服务器切换为主服务器,这就需要人工干预,费事费力,还会造成一段时间内服务不可用.这不是一种推荐的方式,更多时候,我们优先考虑哨兵模式. 一.哨兵 ...
SpringBoot+Redis哨兵模式
最近学习到了Redis的哨兵模式,光看视频还不行,需要自己动手实现一遍才能加深映像,特此记录. 由于没有真实的服务器可以供我操作,所以在虚拟机上启动了3个redis服务,分别占用7001.7002.7 ...
redis 哨兵模式配置
书接上文:https://blog.csdn.net/qq_31618549/article/details/122351041 启用哨兵模式的方法: 1.修改sentinel.conf的配置 pro ...

Redis 哨兵模式安装方法

Redis 哨兵模式安装方法相关推荐

最新文章

热门文章