Strimzi kafka operator pod getting evicted EmptyDir volume "strimzi-tmp" exceeds the limit
See original GitHub issueDescribe the bug
Strimzi kafka operator pod getting evicted Usage of EmptyDir volume "strimzi-tmp" exceeds the limit "1Mi".
Related to https://github.com/strimzi/strimzi-kafka-operator/pull/5375
To Reproduce Steps to reproduce the behavior:
- Create kafka clusters that can’t be scheduled ( causing alot of java error in operator logs )
- Wait
Expected behavior Allow customisation of strimzi-tmp limit
Environment (please complete the following information):
- Strimzi version: 0.25.0
- Installation method: Helm chart
- Kubernetes cluster: Kubernetes 1.19.1
Issue Analytics
- State:
- Created 2 years ago
- Comments:30 (16 by maintainers)
Top Results From Across the Web
In AMQ Streams, the kafka, zookeeper, entity operator pods ...
Issue. AMQ Streams pods are Evicted, and under "Events" it shows: Usage of EmptyDir volume "strimzi-tmp" exceeds the limit "5Mi".
Read more >Configuring Strimzi (In Development)
Ephemeral storage uses emptyDir volumes to store data. An emptyDir volume is created when a pod is assigned to a node. You can...
Read more >Using Strimzi
Ephemeral storage uses emptyDir volumes to store data. ... not exceed access to Kafka brokers based on a byte threshold or a time...
Read more >https://strimzi.io/install/latest?namespace=kafka
A Pod eviction is allowed when the `maxUnavailable` number of pods or fewer are ... strimzi-cluster-operator volumes: - name: strimzi-tmp emptyDir: medium: ...
Read more >Deploying and Upgrading (0.32.0) - Strimzi
For example, kubectl get kafkatopic my-topic or kubectl get kafkatopics . ... Using an emptyDir volume means that its content is strictly related...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@scholzj Argh this is my fault, I added the call to create the CC tmp file here [1] but I never added any calls to delete it. I’ll submit a PR to fix this!
[1] https://github.com/strimzi/strimzi-kafka-operator/blob/main/cluster-operator/src/main/java/io/strimzi/operator/cluster/operator/resource/cruisecontrol/CruiseControlApiImpl.java#L50
Ok, after some investigation internally, and a great tutorial on reading the documentation from a friend here at work, documentation here we realized that the tmpDirSizeLimit should be applied at the kafka spec level as a variable under template. For example:
This solved our issue. I have no idea if that helm chart value I mentioned before is supposed to apply to all pods that use the pod template, but now that I understand how this functions at the pod template level, it’s definitely applying as I would expect when deploying a kafka resource.
Thanks for your help in sorting all this out, @scholzj.