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
2022-11-29T10:10:24.633761052Z stderr F 2022/11/29 10:10:24 [error] 232#232: *92361 FastCGI sent in stderr: "PHP message: PHP Warning: WP Redis: Connection timed out in /opt/bitnami/wordpress/wp-content/object-cache.php on line 1398" while reading response header from upstream, client: cli.en.t.ip , server: _, request: "GET /custom-url HTTP/1.1", upstream: "fastcgi://unix:/opt/bitnami/php/var/run/www.sock:", host: "example.org"
my installation is a WP pods hosted on k8s on Azure and using (Azure cache for Redis) service
I reached out to Azure support and they replied like the following
_The response size was also high during that timeframe. Please note that Redis works best with smaller values. The response size was more than, which could have caused the spike in server load.
The high response size may indicate that client could not be able to deal with this volume timely. A response size with 2.84 M is an extreme larger value and it needs to be reduced.
Optimize your application for a large number of small values, rather than a few large values.
The preferred solution is to break up your data into related smaller values.
I'm also start to having this when my site getting more popular. I see this trend with my 2 popular sites. even getting much more error during last black friday. so there is correlation between traffic and this error?
CRITICAL Maximum execution time of 30 seconds exceeded on this line:
Hello
I am having many alerts in my logs like this
2022-11-29T10:10:24.633761052Z stderr F 2022/11/29 10:10:24 [error] 232#232: *92361 FastCGI sent in stderr: "PHP message: PHP Warning: WP Redis: Connection timed out in /opt/bitnami/wordpress/wp-content/object-cache.php on line 1398" while reading response header from upstream, client: cli.en.t.ip , server: _, request: "GET /custom-url HTTP/1.1", upstream: "fastcgi://unix:/opt/bitnami/php/var/run/www.sock:", host: "example.org"
my installation is a WP pods hosted on k8s on Azure and using (Azure cache for Redis) service
I reached out to Azure support and they replied like the following
_The response size was also high during that timeframe. Please note that Redis works best with smaller values. The response size was more than, which could have caused the spike in server load.
The high response size may indicate that client could not be able to deal with this volume timely. A response size with 2.84 M is an extreme larger value and it needs to be reduced.
Optimize your application for a large number of small values, rather than a few large values.
The preferred solution is to break up your data into related smaller values.
See the post What is the ideal value size range for redis? Is 100 KB too large? for details on why smaller values are recommended._
please advice.
The text was updated successfully, but these errors were encountered: