1、引入依赖redisson的整合很简单,这里直接上代码和演示“读写锁”测试,其他更多的“并发锁”,详情见官方文档(地址见文章末尾),官方写得很详细,这里不赘述了。
2、添加配置类org.redisson redisson
import org.redisson.Redisson;
import org.redisson.api.RedissonClient;
import org.redisson.config.Config;
import org.redisson.config.SingleServerConfig;
import org.springframework.beans.factory.annotation.Value;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
@Configuration
public class MyRedissonConfig {
@Value(value = "${spring.redis.host}")
private String host;
@Value(value = "${spring.redis.port}")
private int port;
@Value(value = "${spring.redis.database}")
private int database;
@Value(value = "${spring.redis.password}")
private String password;
@Bean(destroyMethod = "shutdown")
RedissonClient redisson() {
Config config = new Config();
//Redis多节点
// config.useClusterServers()
// .addNodeAddress("redis://127.0.0.1:6379", "redis://127.0.0.1:7001");
//Redis单节点
SingleServerConfig singleServerConfig = config.useSingleServer();
//可以用"rediss://"来启用SSL连接
String address = "redis://" + host + ":" + port;
singleServerConfig.setAddress(address);
//设置 数据库编号
singleServerConfig.setDatabase(database);
singleServerConfig.setPassword(password);
//连接池大小:默认值:64
// singleServerConfig.setConnectionPoolSize()
return Redisson.create(config);
}
}
读写锁 (ReadWriteLock)
测试要点:演示“读写锁”测试,其他更多的“并发锁”,详情见官方文档(地址见文章末尾),官方写得很详细,这里不赘述了。
- 读锁和写锁共用一个锁key,命名为:readWriteLock; - 读锁接口只负责读, JMeter压测每秒并发20,持续压测; - 写锁接口负责向缓存中写入随机字符串 UUID ,线程睡眠3秒, 模拟业务处理; - 先启动压测并发20读接口,然后发起“写锁请求1”,再发起“写锁请求2”。观察控制台打印的结果。测试代码:
@ResponseBody
@GetMapping("/test/readWriteLock/toRead")
public String toReadLock() {
//获取 锁
RReadWriteLock readWriteLock = redisson.getReadWriteLock("readWriteLock");
RLock rLock = readWriteLock.readLock();
//上 读锁
rLock.lock();
String writeValue = "";
try {
log.info("【读锁-{}】加锁成功,读数据...", Thread.currentThread()
.getId());
writeValue = redisTemplate.opsForValue()
.get("writeValue");
} finally {
log.info("【读锁-{}】解锁成功,uuid={}", Thread.currentThread()
.getId(),writeValue);
//解锁
rLock.unlock();
}
return writeValue;
}
@ResponseBody
@GetMapping("/test/readWriteLock/toWrite")
public String toWriteLock() {
//获取 锁
RReadWriteLock readWriteLock = redisson.getReadWriteLock("readWriteLock");
RLock rLock = readWriteLock.writeLock();
//上 写锁
rLock.lock();
String uuid = UUID.randomUUID()
.toString();
try {
log.info("【写锁-{}】加锁成功,睡眠3秒,模拟执行业务...", Thread.currentThread()
.getId());
Thread.sleep(3000);
redisTemplate.opsForValue()
.set("writeValue", uuid);
} catch (InterruptedException e) {
e.printStackTrace();
} finally {
log.info("【写锁-{}】解锁成功,uuid={}", Thread.currentThread()
.getId(),uuid);
//解锁
rLock.unlock();
}
return "writeLock ok,uuid = " + uuid;
}
测试结果:
并发20读锁接口,观察redis缓存值变化,如下图:
写锁接口请求时,观察redis缓存值变化,如下图:
写锁请求1,控制台打印,如下图:
写锁请求2,控制台打印,如下图:
- ”读-读-读…读“,并发读时,“读锁”相当于没有锁。
- “读-写”或者“写-读”,只要有”写锁“的存在,就要等待”写锁“的释放,才能”读“。写锁时独占锁。
结论:读锁是共享锁,写锁是独占锁。
3、参考地址:- Redis 分布式锁:关于使用 Redlock 算法的官方说明(英文版)
- Redis 分布式锁:关于使用 Redlock 算法的官方说明(中文版)
- Redisson 官方GitHub地址主页
- Redisson 官方说明文档地址



