Loading...

XML

Word

Printable

Target Release:

Future GA
Steps to Reproduce:
Hide

1) AWS deployed OCP4.1 with Broker pods deployed through Broker operator
2) Scaleup applied using configuraiton change and

oc apply -f

3) During the rollout, increasing memory footprint is observed, up until it settles at around 400 MB per POD, which is over 2x over initial memory footprint.
Show
1) AWS deployed OCP4.1 with Broker pods deployed through Broker operator 2) Scaleup applied using configuraiton change and oc apply -f 3) During the rollout, increasing memory footprint is observed, up until it settles at around 400 MB per POD, which is over 2x over initial memory footprint.

Memory footprint initially: ~150-160 megabytes of RAM per POD used

Memory footprint post-scaleup: up to 450 MB per POD

heap dump was created using:

jmap -dump:live,format=b,file=./jmap.heap.dump <java pid>

inside broker container.