redis读写分离
S2B2C 白洞版 · redis读写分离
监控192.168.1.72:6379实例,实例取名为mymaster,当有两个哨兵认为实例下线后,自动进行故障转移
Section titled “监控192.168.1.72:6379实例,实例取名为mymaster,当有两个哨兵认为实例下线后,自动进行故障转移”示例值注意事项:本文中的 IP、域名、账号、密码等仅为示例,请按你的实际环境替换。
- 适用于二开技术团队在对应模块下的开发、调试或配置工作。
- 已拉取对应项目源码并具备基础运行环境。
- 已根据实际环境替换文中的示例配置值。
redis读写分离
Section titled “redis读写分离”redis需要通过主从复制和哨兵模式来实现读写分离,节点设置为一主二从。下面以mall4cloud-aof-redis为例
1. 配置主从复制
Section titled “1. 配置主从复制”配置主节点
redis主节点默认不需要额外配置,只需要确保其网络端口(系统配置为6379)对外可访问。 使用系统部署文档中的配置文件redis.conf即可
配置从节点
从节点需要配置主节点的IP、端口和密码,可使用主节点的conf文件配置,配置两个从节点,补充如下
replicaof <masterip><masterport>masterauth <master-passwd>对应为
replicaof 192.168.1.72 6379masterauth hn02le.34lkdLKD
在docker-compose.yml中根据mall4cloud-aof-redis添加相同配置,分别修改端口为7001,7002启动
mall4cloud-7001-redis: image: redis:8.4.0 container_name: mall4cloud-7001-redis restart: always network_mode: "host" expose: - 7001 volumes: - ./redis/redis7001.conf:/etc/redis/redis7001.conf command: redis-server /etc/redis/redis7001.conf --requirepass hn02le.34lkdLKD启动docker-compose.yml
docker-compose up -d可进入容器查看节点状态,以主节点为例
docker exec -it mall4cloud-aof-redis redis-cli -p 6379auth hn02le.34lkdLKDinfo replication主节点输出以下内容即正常
// 主节点输出role:masterconnected_slaves:2slave0:ip=192.168.1.72,port=7001,state=online,offset=249031856,lag=1slave1:ip=192.168.1.72,port=7002,state=online,offset=249031995,lag=1
// 从节点输出role:slavemaster_host:192.168.1.72master_port:6379master_link_status:up启动成功后,主从节点会自动进行同步,主节点会自动将数据同步到从节点。
2. 配置哨兵模式 sentinel
Section titled “2. 配置哨兵模式 sentinel”共计启动三个实例,分别运行于27001、27002、27003三个端口,以sentinel-27001.conf为例,配置信息如下,其余两个配置文件基本上一致,改一下端口以及pidfile、logfile即可。
port 27001daemonize nopidfile /root/mall4cloud/redis/sentinel-27001.pidlogfile /root/mall4cloud/redis/sentinel-27001.log
# 监控192.168.1.72:6379实例,实例取名为mymaster,当有两个哨兵认为实例下线后,自动进行故障转移sentinel monitor mymaster 192.168.1.72 6379 2sentinel auth-pass mymaster hn02le.34lkdLKD# 服务不可达时间,心跳超过这个时间,sentinel将认为节点挂了sentinel down-after-milliseconds mymaster 5000sentinel failover-timeout mymaster 60000sentinel parallel-syncs mymaster 1在docker-compose.yml配置中添加三个实例
sentinel-27001-redis: image: redis:8.4.0 container_name: sentinel-27001-redis restart: always network_mode: "host" expose: - 27001 volumes: - ./redis/sentinel-27001.conf:/etc/redis/sentinel-27001.conf - /root/mall4cloud/redis:/root/mall4cloud/redis command: redis-sentinel /etc/redis/sentinel-27001.启动docker-compose.yml,启动后进入容器查看
docker exec -it sentinel-27001-redis redis-cli -p 27001info sentinel输入结果为:
sentinel_masters:1sentinel_tilt:0sentinel_tilt_since_seconds:-1sentinel_running_scripts:0sentinel_scripts_queue_length:0sentinel_simulate_failure_flags:0master0:name=mymaster,status=ok,address=192.168.1.72:7002,slaves=2,sentinels=3启动成功后,三个实例会自动进行监控,当主节点挂掉后,会自动进行故障转移。
在项目pom.yml中引入依赖
<commons-pool2.version>2.12.1</commons-pool2.version> <lettuce.version>6.2.6.RELEASE</lettuce.version>
<dependency> <groupId>org.apache.commons</groupId> <artifactId>commons-pool2</artifactId> <version>${commons-pool2.version}</version> </dependency> <dependency> <groupId>io.lettuce</groupId> <artifactId>lettuce-core</artifactId> <version>${lettuce.version}</version> </dependency>在mall4cloud-common模块中mall4cloud-common-cache的pom.yml添加依赖
<dependency> <groupId>io.lettuce</groupId> <artifactId>lettuce-core</artifactId> </dependency> <dependency> <groupId>org.apache.commons</groupId> <artifactId>commons-pool2</artifactId> </dependency>修改RedisCacheConfig类,并添加以下代码
@Bean public RedisConnectionFactory createRedisConnectionFactory(RedisProperties redisProperties) { // 判断是否配置了哨兵模式 if (redisProperties.getSentinel() != null && redisProperties.getSentinel().getMaster() != null) { // 哨兵模式配置 var sentinelConfig = new RedisSentinelConfiguration() .master(redisProperties.getSentinel().getMaster()); // 添加哨兵节点(使用 Java 17 的 Stream API 优化) redisProperties.getSentinel().getNodes().stream() .map(node -> node.split(":")) .forEach(parts -> sentinelConfig.sentinel(parts[0], Integer.parseInt(parts[1]))); if (Objects.nonNull(redisProperties.getDatabase())) { sentinelConfig.setDatabase(redisProperties.getDatabase()); } else { sentinelConfig.setDatabase(0); } if (Objects.nonNull(redisProperties.getPassword())) { sentinelConfig.setPassword(RedisPassword.of(redisProperties.getPassword())); } // 配置读写分离策略:优先从副本读取 var clientConfig = LettuceClientConfiguration.builder() .readFrom(ReadFrom.REPLICA_PREFERRED) .build(); return new LettuceConnectionFactory(sentinelConfig, clientConfig); } else { // 单节点模式配置 var standaloneConfig = new RedisStandaloneConfiguration(); standaloneConfig.setHostName(redisProperties.getHost()); standaloneConfig.setPort(redisProperties.getPort()); standaloneConfig.setPassword(RedisPassword.of(redisProperties.getPassword())); standaloneConfig.setDatabase(redisProperties.getDatabase()); var clientConfig = LettuceClientConfiguration.builder() .build(); return new LettuceConnectionFactory(standaloneConfig, clientConfig); } }修改AofRedisConfig类的AofRedisConfig方法,添加以下代码
public AofRedisConfig(AofRedisBO aofRedisBO) {
if (StrUtil.isBlank(aofRedisBO.getRedisAddr())) { throw new YamiShopBindException("请在yml配置好 aofRedis 的配置,见 com.yami.shop.common.bo.AofRedisBO"); }
Config config = new Config(); if (BooleanUtil.isTrue(aofRedisBO.getSentinel())) { // 哨兵模式 SentinelServersConfig sentinelServersConfig = config.useSentinelServers(); sentinelServersConfig.setMasterName(aofRedisBO.getMasterName()); List<String> list = Arrays.stream(aofRedisBO.getRedisAddr().split(",")).map(ip -> "redis://" + ip).toList(); if (aofRedisBO.getDatabase() != null) { sentinelServersConfig.setDatabase(aofRedisBO.getDatabase()); } else { sentinelServersConfig.setDatabase(0); } if (StrUtil.isNotBlank(aofRedisBO.getPassword())) { sentinelServersConfig.setPassword(aofRedisBO.getPassword()); } sentinelServersConfig.setSentinelAddresses(list); } else { // 单机 SingleServerConfig singleServerConfig = config.useSingleServer(); if (StrUtil.isNotBlank(aofRedisBO.getPassword())) { singleServerConfig.setPassword(aofRedisBO.getPassword()); } if (aofRedisBO.getDatabase() != null) { singleServerConfig.setDatabase(aofRedisBO.getDatabase()); } else { singleServerConfig.setDatabase(0); } singleServerConfig.setAddress("redis://" + aofRedisBO.getRedisAddr()); }
redissonClient = Redisson.create(config); LOGGER.info("创建redisson, redisson={}", redissonClient);
stringRedisTemplate = new StringRedisTemplate();
stringRedisTemplate.setValueSerializer(StringRedisSerializer.UTF_8); stringRedisTemplate.setKeySerializer(StringRedisSerializer.UTF_8); stringRedisTemplate.setConnectionFactory(new RedissonConnectionFactory(redissonClient));
stringRedisTemplate.afterPropertiesSet(); }修改nacos服务中配置文件application.yml的redis连接配置,端口和密码配置根据实际情况配置
data: redis: sentinel: master: mymaster nodes: - 192.168.1.72:27001 - 192.168.1.72:27002 - 192.168.1.72:27003 password: hn02le.34lkdLKD database: 7修改nacos服务中mall4cloud-product.yml的aofredis连接配置
redis: aof: sentinel: true master-name: mymaster database: 8 redis-addr: 192.168.1.72:27001,192.168.1.72:27002,192.168.1.72:27003 password: hn02le.34lkdLKD保存后重启服务即可。
- 根据文中步骤完成后,确认对应功能可访问或服务可正常启动。
- 可先查看故障排查索引:
../../04-故障排查/README.md
- 当前目录索引:
README.md