пн, 19 сент. 2022 г. в 20:47, Tim Düsterhus <t...@bastelstu.be>:
> Hi > > recently our HAProxy nodes started handling long-running HTTP > connections (similar to WebSockets). This causes old workers to stay > around for several days after a reload. > > This isn't too bad from a memory perspective, we have sufficient RAM to > keep around the old processes until the connections die naturally. It's > much worse from a CPU perspective: The old workers appear to still > perform health checks and DNS lookups and this takes away precious > resources from the active workers. > What are those connections ? Is it a sequence of several requests within an established keepalive connection? if so, probably it can be good idea to limit number of requests per keepalive session (it is no harm to terminate session after some successful request) > > My understanding is that the old workers will only handle existing > connections and thus will never need to connect to a backend (server) > again. Thus it should not be necessary to waste CPU on DNS lookups and > health checks for a stopping worker. > > Am I missing something here? > > Best regards > Tim Düsterhus > >
