PING Command execution timeout for command about redisson HOT 14 CLOSED

Fixed in #5493 Try 3.26.1 version

@mrniko your swift response is greatly appreciated. We will be testing with the latest version, 3.26.1. Thank you!

from redisson.

Fixed in #5493
Try 3.26.1 version

from redisson.

@mrniko While this issue has been reported across various Redisson versions, it specifically emerges in a particular environment despite multiple deployments using the same Redisson version (3.20.1). Our aim is to comprehend the specific scenarios leading to this problem. By doing so, we can proactively prevent or take necessary actions to mitigate the occurrence of this issue in other environments.

Issue reported in 3.17.6 version : #4441
PR : b320f19

Issue reported in 3.23.4 version : #5371
PR : 6056656

Issue reported in 3.25.0 version : #5493
PR : e7bdea6

Thanks

from redisson.

@Venkat-C-J

I suggest you to check the network of this environment.

from redisson.

Same error in latest 3.27.0 version

org.redisson.client.RedisTimeoutException: Command execution timeout for command: (PING), params: [], Redis client: [addr=rediss://xxxx:6380]
at org.redisson.client.RedisConnection.lambda$async$0(RedisConnection.java:253)
at io.netty.util.HashedWheelTimer$HashedWheelTimeout.run(HashedWheelTimer.java:715)
at io.netty.util.concurrent.ImmediateExecutor.execute(ImmediateExecutor.java:34)
at io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:703)
at io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:790)
at io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:503)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.base/java.lang.Thread.run(Thread.java:840)

from redisson.

@ShriramDeshkar

Did you try to increase ping timeout interval?

from redisson.

I have not set any timeout interval explicitly ...I m using org.redisson.config.Config to set configuration of RedissonClient object .....what is your recommendation ? What value shall we use while setting timeout interval ? and which method to use setTimeout() or setConnectTimeout() ?

from redisson.

@mrniko any update on this issue ?

from redisson.

@mrniko any update on this issue ?

my redis version is 7.2.4，redissson version is 3.27.1，without any questions，i think it is redisson version and redis version don‘t match

from redisson.

@ShriramDeshkar

Sorry, unable to reproduce it.

@pious68

What do you mean PING command is compatible with any version of Redisson and Redis

from redisson.

Hi @mrniko,

We are currently facing issues across all environments. To resolve the problem, we have consulted Amazon regarding possible network issues. However, they have confirmed that there are no current network-related issues. In addition, we have attempted to fix the problem by configuring the Idle Timeout to 60 seconds on Redis Cluster. Despite these measures, we are still encountering issues.

from redisson.

@Venkat-C-J

Can you share the Redisson config?

from redisson.

I encountered the same error and initially had Redis version 6. Upgrading to the latest version resolved the issue for me. It seems that compatibility or specific fixes in the newer Redis versions may address this error. It might be worth checking if there’s a particular version or configuration change that specifically targets this issue.


from redisson.

@Ftrybe
There are no fixes in Redisson related to specific Redis versions. I guess Redis redeployment in cloud may also helped to resolve the issue.

from redisson.