-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
-
No
-
---
-
---
-
MK - Sprint 225
Problem Statement
During an incident, we tried to use the following SOP to collect a Java heap dump from a Kafka pod.
The SOP failed in two ways:
- The SOP assumes the availability of the ps command. The ps command isn't available in the image. The jps command is available.
- The SOP assumes /tmp is sufficiently large to take a Java Heap Dump. In the case of a Kafka heap dump, this wasn't the case.
What
Address the defects in the SOP ensuring that the SOP is compatible with all the Java images used by Managed Kafka. Automated mechanisms to make sure this doesn't regress would be desirable too.
How
TBD
- depends on
-
MGDSTRM-9377 Release Fleet Shard Operator 0.27.0
- Closed
- is blocked by
-
MGDSTRM-8824 RHOSAK Java-based images should include JDK rather than JRE + install procps
- Closed
-
MGDSTRM-8904 kas-fleetshard Java-based images should include JDK rather than JRE + install procps
- Closed
- mentioned on