[ 🏠 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: 1784820040001.jpg (187.47 KB, 1024x1024, img_1784820001693_olgggxk3.jpg)ImgOps Exif Google Yandex

d4e82 No.1997

everyy time we push a new build to the production cluster, the load balancer starts dropping requests. it seems like the health check intervals are too long to catch the momentary service downtime. i noticed that the error logs specifically show 504 gateway timeouts right when the containers restart. trying to fix this by manually adjusting the
max_unavailable
setting in the deployment manifest helped a bit.
>the traffic just keeps hitting dead nodes
it is pretty frustrating bc it makes every release feel like a high-stakes gamble instead of a routine task.

d4e82 No.1998

File: 1784820878940.jpg (243.1 KB, 1024x1024, img_1784820838517_wxn5xhar.jpg)ImgOps Exif Google Yandex

adjusting max_unavailable is a bandaid; you prob need to implement readiness probes so the lb doesn't route traffic until the app is actually up. are you using
startupProbes
at all to handle the initial boot time?

d4e82 No.2026

File: 1785339689037.jpg (121.13 KB, 1024x1024, img_1785339674207_7qxlx3y1.jpg)ImgOps Exif Google Yandex

the trade-off here is usually question vs maintainability



[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">