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
But one instance (10.0.1.11:7013) is getting ~5x higher load then other instances. I have run redis monitor on each instance for 5 seconds and check amount of GET/SETEX/ECHO commands.
Each instance has similar amount of GET/SETEX/ECHO:
for some unknown reason, this instance is getting 10x more ECHO commands than SETEX/GET resulting in 5x higher total load.
Setting redis.pconnect.echo_check_liveness = 0
fixes the problem, so the issue is for sure in persistent liveness check. But why only one of 12 instances got 10x more ECHO commands?
I'm seeing this behaviour on
OS: RHEL9
Redis: 6.2.7-1.el9
PHP: 8.2.12-1.el9.remi
phpredis: php-pecl-redis5-5.3.7-2.el9.remi
Steps to reproduce, backtrace or example script
I've checked
There is no similar issue from other users
Issue isn't fixed in develop branch
The text was updated successfully, but these errors were encountered:
bitactive
changed the title
Redis sessions, when set with the persistent flag and 'echo_check_liveness,' generate an enormous number of echo calls
Redis sessions, when set with the persistent flag and 'echo_check_liveness', generate an enormous number of echo calls
Nov 3, 2023
bitactive
changed the title
Redis sessions, when set with the persistent flag and 'echo_check_liveness', generate an enormous number of echo calls
Redis sessions, when set with the persistent flag and echo_check_liveness, generate an enormous number of echo calls
Nov 3, 2023
Expected behaviour
When phpredis used as session handler it should ECHO similar amount of times as GET/SETEX on each server.
Actual behaviour
One of 12 redis instances got 10x more ECHO commands than others. Disabling echo_check_liveness fixes the problem.
Steps to reproduce, backtrace or example script
I have redis session handler to multiple redis instances using following string:
But one instance (10.0.1.11:7013) is getting ~5x higher load then other instances. I have run redis monitor on each instance for 5 seconds and check amount of GET/SETEX/ECHO commands.
Each instance has similar amount of GET/SETEX/ECHO:
Except one: 10.0.1.11:7013
for some unknown reason, this instance is getting 10x more ECHO commands than SETEX/GET resulting in 5x higher total load.
Setting
redis.pconnect.echo_check_liveness = 0
fixes the problem, so the issue is for sure in persistent liveness check. But why only one of 12 instances got 10x more ECHO commands?
I'm seeing this behaviour on
Steps to reproduce, backtrace or example script
I've checked
develop
branchThe text was updated successfully, but these errors were encountered: