You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Karapace 3.4.x it is possible to send HTTP requests to the Kafka REST Proxy causing Karapace process to take almost all CPU (a single core). Additionally Karapace causes high load ~30-50% in Kafka. The situation remain even if the process is left alone (no traffic sent to it) for hours.
The issue was found out when running some manual testing using consumers that are not clean up correctly. The exact steps are quite hard to explain here, since the tester and the exact test steps are a part of a larger project that cannot be shared here,
What else do we need to know?
Karapace 3.4.x has the issue. It's unknown whether older versions have it.
The text was updated successfully, but these errors were encountered:
First fetch min bytes negative values was misconfiguration even for
kafka-python earlier, but worsened with aiokafka. Add extra
configuration for aiokafka timeout settings tuning.
Fixes#488
What happened?
In Karapace 3.4.x it is possible to send HTTP requests to the Kafka REST Proxy causing Karapace process to take almost all CPU (a single core). Additionally Karapace causes high load ~30-50% in Kafka. The situation remain even if the process is left alone (no traffic sent to it) for hours.
The issue was found out when running some manual testing using consumers that are not clean up correctly. The exact steps are quite hard to explain here, since the tester and the exact test steps are a part of a larger project that cannot be shared here,
What else do we need to know?
Karapace 3.4.x has the issue. It's unknown whether older versions have it.
The text was updated successfully, but these errors were encountered: