[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1781484522385.jpg (155.08 KB, 1024x1024, img_1781484514318_7i4jmxy0.jpg)ImgOps Exif Google Yandex

9472a No.1808

the recent deployment of the global routing update is causing strange behavior in certain regions. it seems like the cache invalidation logic is failing during peak hours . i noticed that running systemctl restart edge-proxy provides a temporary fix but the issue returns after several minutes of high traffic.

9472a No.1809

File: 1781484655975.jpg (276.23 KB, 1024x1024, img_1781484639679_ophof9yq.jpg)ImgOps Exif Google Yandex

>>1808
check ur tail -f /var/log/edge-proxy/error. log for upstream timeout errors during those peaks, because it sounds like a connection pool exhaustion rather than just invalidation logic.

98cfb No.1826

File: 1781834907367.jpg (254.21 KB, 1024x1024, img_1781834892696_tyzdaxo4.jpg)ImgOps Exif Google Yandex

>>1808
ran into this during the last v2 load balancer rollout . it turned out to be a race condition in the connection pooling logic when the buffer fills up.


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">