Two separate CpuBoundWork semaphores – HTTP

Icinga / icinga2

The core of our monitoring platform with a powerful configuration language and REST API.

https://icinga.com/docs/icinga2/latest

GNU General Public License v2.0

2k stars 574 forks source link

Open Al2Klimov opened 5 months ago

Al2Klimov commented 5 months ago

One of our customers is DDoSing their Icinga 2 via /v1/hosts (a lot of hosts btw.). That locks up cluster communication entirely.

The separate HTTP CpuBoundWork gets e.g. 1 slot or 1/2 of all so that it doesn't bother the cluster.

Put actual processing of HTTP requests in a queue.

ref/IP/48306

Al2Klimov commented 3 months ago

Describe alternatives you've considered

Put actual processing of HTTP requests in a queue.

Actually the standard thread pool would be nice, the coroutine could suspend itself during processing, just like in #9990

Al2Klimov commented 1 week ago

Maybe Icinga DB even deserves its own I/O, isolated from everything else. So that it doesn't influence cluster communication throughput.