Meet “Connection pool reached max wait queue size” error when using redis reactive #43981
-
Hi, I have a method like this: public class MyRedisService {
@Inject
ReactiveRedisDataSource reactiveRedisDataSource;
...
public Uni<Void> set(String key, String value) {
logger.debug("REDIS set -> " + key + " / " + value);
return reactiveRedisDataSource.value(String.class).set(TS_REDIS_PREFIX + key, value);
}
} And the above method is called recursively: public void doSomething() {
myRedisService.set(taskId).subscribe().with(
ok -> { ... },
err -> { doSomething() },
);
} And if the recursive level is too deep(ocaasionally), it will throw error like this:
Is there anyway I can solve this? For example, is there anyway I can increase the connection pool, or if I can configure the |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
/cc @Ladicek (redis), @cescoffier (redis), @machi1990 (redis) |
Beta Was this translation helpful? Give feedback.
-
You can configure the max number of commands waiting to be executed with quarkus.redis.max-pool-waiting=24. 24 is the default value. |
Beta Was this translation helpful? Give feedback.
You can configure the max number of commands waiting to be executed with quarkus.redis.max-pool-waiting=24. 24 is the default value.