Open LucyWengCSS opened 5 years ago
Looks like you are running both Jedis and scala-redis - I am not sure if the issue has something to do with this.
Regarding
AUTH was never sent within the timeout period
can there be any network issues that caused the timeout ?
I am just guessing as this looks like a local environment specific issue as it has been running for 9 months without any issue ..
Hi Debasish,
Thanks so much for your help in the issue.
The information is very useful. We agree that the intermittent network issue may cause the NOAUTH exception in the client and we already add the try-catch logic in our application.
Thanks again.
Hi Team,
Issue Definition: Exceptions throwed by spack jobs: ncom.redis.RedisProtocolParsingException: NOAUTH Exception Cache
Recurrence: The binary was running without any errors since the past 9 months. However, since 9th Jun the error NOAUTH Exception Cache can be observed. Occurrence of this issue is very less. Most of the time this is working fine.
Client SDK: Jedis 2.8.0 and Scala-redis_2.11.
Investigation: By checking the server side logs,the NOAUTH issue is “Closing unauthenticated client, either AUTH didn't succeed or AUTH was never sent within the timeout period”, which means AUTH was not sent on some of the connections.
Could you please provide us with any insights about troubleshooting the issue?
Thanks