-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seata接入Redis哨兵集群失败 #4161
Comments
client端没有使用redis,tc端的redis用的Jedis,跟spring-boot-starter-data-redis无关,如果你是client端连不上redissentinel,那么跟seata是无关的 |
是我上面的说明写的有点偏差,seata1.4.2版本里面用的是jedis,服务端配置redis哨兵模式的时候,假如哨兵节点设置了密码,seata服务端是连接不是redis的 |
欧克,很荣幸能参与进来 |
@zzhangzd 还在吗?这个pr还没提呦 |
plz assign to me |
Ⅰ. Issue Description
Seata1.4.2版本,接入Redis哨兵集群的时候,假如哨兵节点配置密码的话,jedis客户端接入失败,报权限认证失败的错误。jedis客户端不支持sentinel节点设置密码,JedisSentinelPool 类中,74行 sentinelPassword 项默认为null导致的。
假如将客户端改为spring-boot-starter-data-redis, 2.3.4.RELEASE版本以上可配置sentinelPassword
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
The text was updated successfully, but these errors were encountered: