You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're using lettuce-core 5.3.7.RELEASE in cluster mode (async api), and we have two docker images which are based on java 1.8.0_101-b13 and 1.8.0_201-b09(I don't have the docker file for these images, but the main difference should be java version).
Everything on 101 image is fine, but timeout problem happens in 201 image. On 201 image, after our application starts, the redis call just hangs, we have tried different timeout settings, but we don't even get a timeout exception. After several minutes(different duration each time, no obvious pattern), the redis client gets back to normal, redis command works just fine.
On 201 image during hangs period, we noticed the Recv-Q (output of ss command) value of connection to redis clsuter was not zero and wouldn't decrease for sometime, but same situation never happens on 101 image.
Any thoughts on how should I troubleshoot this problem? Thanks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We're using
lettuce-core 5.3.7.RELEASEin cluster mode (async api), and we have two docker images which are based on java1.8.0_101-b13and1.8.0_201-b09(I don't have the docker file for these images, but the main difference should be java version).Everything on
101image is fine, buttimeoutproblem happens in201image. On201image, after our application starts, the redis call just hangs, we have tried different timeout settings, but we don't even get a timeout exception. After several minutes(different duration each time, no obvious pattern), the redis client gets back to normal, redis command works just fine.On
201image duringhangsperiod, we noticed theRecv-Q(output ofsscommand) value of connection to redis clsuter was not zero and wouldn't decrease for sometime, but same situation never happens on101image.Any thoughts on how should I troubleshoot this problem? Thanks.
Beta Was this translation helpful? Give feedback.
All reactions