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
With the introduction of CLIENT SETINFO in connection.py in 5.0.0 (Add support for CLIENT SETINFO (#2857)), the INFO commandstats now reports cmdstats_client which now increments failed_calls on every connection.
SETINFO was only added in Redis 7.2 therefore 5.0.0 will consider any connection on a Redis < 7.2 as a failed_call.
It seems to have no impact on Redis or the functionality whatsoever, other than incrementing the failed_calls counter and it happens on every connect. Although it does have an impact on telemetry and monitoring.
A very big thanks to Steve L (admin on Redis discord) for the very helpful assistance in identifying the cause of the issue here.
The text was updated successfully, but these errors were encountered:
earthgecko
added a commit
to earthgecko/redis-py
that referenced
this issue
Dec 22, 2023
@earthgecko If you want to skip CLIENT SETINFO you can set the library name and version to None (here, it sends the command only if the information exist, and yes, by default it exist)
Version:
redis-stack-server: redis-stack-server-6.2.6-v7.rhel8.x86_64.tar.gz
redis_version:6.2.12
redis-py: 5.0.1
Platform: Python 3.8.17 on CentOS Stream 8
Description:
With the introduction of
CLIENT SETINFO
in connection.py in 5.0.0 (Add support for CLIENT SETINFO (#2857)), theINFO commandstats
now reportscmdstats_client
which now incrementsfailed_calls
on every connection.SETINFO
was only added in Redis 7.2 therefore 5.0.0 will consider any connection on a Redis < 7.2 as a failed_call.It seems to have no impact on Redis or the functionality whatsoever, other than incrementing the
failed_calls
counter and it happens on every connect. Although it does have an impact on telemetry and monitoring.A very big thanks to Steve L (admin on Redis discord) for the very helpful assistance in identifying the cause of the issue here.
The text was updated successfully, but these errors were encountered: