redis可重入分布式锁
交易系统 使用 redis分布式锁 防止重复提交订单
加锁
public String tryLock(String key, long expire) {
String requestId = UUID.randomUUID().toString();
try {
RedisCallback<String> callback = (connection) -> {
JedisCommands commands = (JedisCommands) connection.getNativeConnection();
return commands.set(key, requestId, "NX", "PX", expire);
};
String result = (String) redisTemplate.execute(callback);
if (StringUtils.isNotEmpty(result)) {
return requestId;
} else {
//再次检查
RedisCallback<String> query = (connection) -> {
JedisCommands commands = (JedisCommands) connection.getNativeConnection();
return commands.get(key);
};
String reqId = (String)redisTemplate.execute(query);
if(requestId.equals(reqId)){
return requestId;
}
return null;
}
} catch (Exception e) {
LOGGER.error("set redis occured an exception", e);
}
//redis出问题 默认放过
return requestId;
}
解锁
LUA 脚本保证 拿锁+删除锁的 原子性
private static final String UNLOCK_LUA =
"if redis.call('get',KEYS[1]) == ARGV[1]\n" +
"then\n" +
" return redis.call('del',KEYS[1])\n" +
"else\n" +
" return 0\n" +
"end";
public boolean releaseLock(String key, String requestId) {
// 释放锁的时候,有可能因为持锁之后方法执行时间大于锁的有效期,此时有可能已经被另外一个线程持有锁,所以不能直接删除
try {
// 使用lua脚本删除redis中匹配value的key,可以避免由于方法执行时间过长而redis锁自动过期失效的时候误删其他线程的锁
// spring自带的执行脚本方法中,集群模式直接抛出不支持执行脚本的异常,所以只能拿到原redis的connection来执行脚本
RedisCallback<Long> callback = (connection) -> {
Object nativeConnection = connection.getNativeConnection();
// 集群模式和单机模式虽然执行脚本的方法一样,但是没有共同的接口,所以只能分开执行
// 集群模式
if (nativeConnection instanceof JedisCluster) {
return (Long) ((JedisCluster) nativeConnection).eval(UNLOCK_LUA, Arrays.asList(key), Arrays.asList(requestId));
}
// 单机模式
else if (nativeConnection instanceof Jedis) {
return (Long) ((Jedis) nativeConnection).eval(UNLOCK_LUA, Arrays.asList(key), Arrays.asList(requestId));
}
return 0L;
};
Long result = (Long) redisTemplate.execute(callback);
return result != null && result > 0;
} catch (Exception e) {
LOGGER.error("release lock occured an exception", e);
}
return false;
}