Replies: 2 comments 2 replies
-
What exactly do you think is a Strimzi bug on this? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Can you share kafka community group details.
…On Tue, 9 Sept, 2025, 13:00 Paolo Patierno, ***@***.***> wrote:
I can't see it as a Strimzi bug and should be asked to the Apache Kafka
community imho.
—
Reply to this email directly, view it on GitHub
<#11846 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC7EJS2QXL57GS6UMCZ4KS33RZ62VAVCNFSM6AAAAACF72L33SVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZUHAZDQNQ>
.
You are receiving this because you authored the thread.Message ID:
<strimzi/strimzi-kafka-operator/repo-discussions/11846/comments/14348286@
github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Bug Description
String 0.39 and kafka version 3.5.1. Trying to simulate log.segment.bytes, retention value set. Created a topic without retention. set the retention at broker level. Ran the traffic towards kafka broker level. modified the log.segment.bytes. monitored the disk usage. the pvc getting filled and lead to crashloopbackoff. Is there any configuration change that helps preventing disk usage high. Is retention value should be increased.
Steps to reproduce
Expected behavior
Disk usage should not increase. That is the expectation.
Strimzi version
0.39
Kubernetes version
1.32
Installation method
No response
Infrastructure
No response
Configuration files and logs
No response
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions