Hi,
I did some research on this and opened a JIRA ticket with my findings.
If anyone can have a look at it, that would be great :)
https://issues.apache.org/jira/browse/KAFKA-12431
Thanks,
Peter
On Mon, 1 Mar 2021 at 08:35, Ismael Juma wrote:
> The last message format version was in 0.11. Once
The last message format version was in 0.11. Once you have the flame graph,
please file a JIRA with it attached. CPU usage is expected to be lower in
the new version, not higher.
Ismael
On Fri, Feb 26, 2021, 9:59 AM Jhanssen Fávaro
wrote:
> Not sure if this applies only to this 0.10 version.
>
Not sure if this applies only to this 0.10 version.
[image: image.png]
Regards.
On Fri, Feb 26, 2021 at 2:54 PM Péter Sinóros-Szabó
wrote:
> Hi,
>
> No, CPU increase shouldn't be there. Upgrades usually bring lower CPU
> usage.
>
> And yes, I followed the upgrade protocol as it is described in
Hi,
No, CPU increase shouldn't be there. Upgrades usually bring lower CPU usage.
And yes, I followed the upgrade protocol as it is described in the
documentation, I got the CPU increase when I upgraded the 1st instance as
the first step.
Cheers,
Peter
On Fri, 26 Feb 2021 at 18:35, Jhanssen Fáva
Hi,
thanks, yes I planned to run a profiler on it, Opsian to be exact, to see
what's going on, but the async profiles is a good option as well.
I just wanted to ask if anyone experienced this before.
I will get back here if I find something useful.
Peter
On Fri, 26 Feb 2021 at 18:34, Alex Woolf
Hi Peter,
I am on the same, a lot of questions about the Kafka's upgrade process. But
looks like tha this CPU Increase is expected, at least while you don't
finish every broker upgrade.
In this case, when you say you didn't change the version, you say that for
any brokers right ?
Basically, you s
It might be worth attaching a profiler to see what's eating up all the
cycles, Peter.
I used this recently, and it turned out that my Prometheus monitoring was
the culprit: https://github.com/jvm-profiling-tools/async-profiler
>From my terminal history:
cd /tmp
wget
https://github.com/jvm-profil
Hi,
I just upgraded from Kafka 2.4.1 to 2.6.1 and I see huge CPU usage on the
broker after the upgrade. Upgrade in this case means that I only bumped the
broker version on 1 of the brokers out of the 6 and didn't change the
protocol or message format versions. Before the upgrade, it used about 35%
