|
|
相关文章推荐
|
乖乖的小摩托 · 23. 深度解密 Redis ...· 2 月前 · |
|
|
无邪的猴子 · Redis 数据类型 | · 2 月前 · |
|
|
灰常酷的炒面 · Document：createTextNod ...· 1 年前 · |
|
|
侠义非凡的椰子 · 将用户db迁移到Subversion ...· 2 年前 · |
|
|
打酱油的大蒜 · css 父元素与子元素同高-掘金· 2 年前 · |
|
|
霸气的烈马 · Sequelize中用group ...· 3 年前 · |
Hi,
RedisURI has a "timeout for synchronous command execution".
But when using the async API, calling get with a timeout value greater than the redis URI timeout does not work, the redis URI timeout is used no matter what.
Does that mean the redis URI timeout Javadoc is actually misleading and is rather a maximum timeout for any command whether the used API is sync or async?
Another issue I have is integrating lettuce with brpop: brpop has a timeout of its own at Redis protocol level, but actually when passing 0 for "wait forever", the java API throws a timeout exception after the redis uri configured timeout (which defaults to 1 minute). How can I avoid that redis URI timeout to take over?