lettuce icon indicating copy to clipboard operation
lettuce copied to clipboard

Advanced Java Redis client for thread-safe sync, async, and reactive usage. Supports Cluster, Sentinel, Pipelining, and codecs.

Results 277 lettuce issues
Sort by recently updated
recently updated
newest added

hello, when we using the spring data redis and encounter the below issues, the luttuce throw out the issues(this could be find in the bellow erro msg), ![image](https://github.com/spring-projects/spring-data-redis/assets/7547133/2c2eac59-356f-49c2-b236-2f28f76d45ae) Is there...

status: waiting-for-feedback
status: feedback-reminder

## Bug Report #### Current Behavior When using lettuce, our service periodically reports a RedisCommandTimeoutException when redis commands are executed. We caught found that after establish a TCP connection, the...

status: waiting-for-feedback

## Bug Report We have seen an issue whether thread has got stuck waiting for getConnection future to complete. Looks like it is waiting for method connectClusterAsync to complete but...

type: bug

How to monitor the status parameters of the Lettuce connection pool, such as maximum idle connections and minimum idle connections?

status: waiting-for-feedback

When we switch the Redis host as a failover step, the Lettuce API is taking way longer for all operations on the newly switched host. The command metrics do not...

for: team-attention

## Feature Request The existing implementation of the **get** method in the **ClientSideCaching** class fails to provide a mechanism that guarantees the exclusive access of a single thread to fetch...

type: bug

Similar to redis-py, can a nonatomic version of MSET and MGET be implemented in Lettuce? Testing 5 keys with mget on Lettuce took about 20-40ms, whereas the same test on...

type: enhancement

Our objective is to use LettuceConfiguration for Redis Sentinel server to obtain the Redis lock and for caching @Cachable. We are having the following problem. ``` : Failed to complete...

status: waiting-for-feedback

In our company, we operate a 6 node redis cluster setup (3 masters & 3 slaves), and we are considering using Lettuce. An issue came up when testing a scenario...

for: team-attention

## Feature Request ([branch](https://github.com/mtheos/lettuce-core/tree/auto-batch)) Hi team, have you considered periodic-flushing/auto-batching as a middle ground between auto and manual flushing? I'm aware of the `@Batch` annotation for the command interface, but...

type: enhancement
status: waiting-for-feedback