@Cacheable. I'm randomly seeing
connetcion reest by peerissues and then this issue is propagated to client as 500. I'm wondering whether lettuce cuould be somehow configured to do a retry on this type of error (some exponencial backoff would be perfect) or I need to do it on my own wrapping cached method in some
CommandHandler.exceptionCaughtperforms the exception propagation into the head command which is currently active.
ChannelInboundHandlerthat handles the exception before
LettuceConnectionConfigurationso is there any possibility to change something?
ClientResourcesbean with a bit of customization
IOExceptionsare followed by a disconnect signal. Lettuce auto-reconnects by default and so all commands that were sent and that didn't time out will be retried.
validateConnection. So if I add a pool to lettuce and somehow set the
validateConnection=truethen each time then connection is being used it's validated before. So if there is such
connection reset by peeris it possible that this won't be propagated to client? I know that there are going to be 2 round trips (validation + actuall call).
io.lettuce.core.RedisException: java.lang.NoSuchMethodError: 'void io.netty.util.concurrent.PromiseCombiner.<init>(io.netty.util.concurrent.EventExecutor)'everytime I close my
RedisClientand I think this is because I have a piece of software which already uses Netty and so already defined it. Now I don't know how to fix this, as it seems like both use different versions. Can someone help me out?
Caused by: io.lettuce.core.RedisCommandExecutionException: ERR unknown command `CONFIG`, with args beginning with: `GET`, `notify-keyspace-events`,. Is this related to spring-projects/spring-session#124 ? I have found no explicit references to Spring Session or Lettuce in the code.
CONFIGand Spring Session tries to update the Redis server to enable keyspace events.