Hello,
just wondering, were there any particular changes in 3.10 or 3.11 in how RabbitMQ management API handles HTTP queries? Maybe something internally in core or RabbitMQ management plugin, which could affect HTTP query performance (directly or indirectly)?
We have a Java application which queries management API every few minutes, and then tries to verify queue/exchange/permission state. At the moment we have something like 8,5k queues and the process checks every queue separately. If something is not right Java application then creates/re-creates queues according to the tenant data in our internal Postgres database. This is to ensure that all our RabbitMQ level tenants are healthy.
After we’ve upgraded from 3.9 to 3.11 CPU load on the cluster during these health checks increased 20-30%.
Any pointers are much appreciated!
--
Best Regards,
Vilius Šumskas
Rivile
IT manager