Hello, Background: We are currently running our application using a very old version of hornetq. As part of our migration to Kubernetes, we wanted to try to use activemq-artemis as a drop-in replacement for this old broker with some newer monitoring features. Our application is not very big in terms of the number of messages/consumers. We are usually only generating maybe tens of messages a second at peak and we have less than 50 consumers in our qa environment. Most of the time we actually aren’t even sending any messages.
Problem: We have given artemis roughly the same cpu/memory we have on hornet but we are finding that over time the cpu just keeps increasing until it hits the limit we give it in Kubernetes. At that point the service continues to work but can be a bit spotty. However, we completely lose the web console as well as the jmx exporter so we have no visibility/monitoring. Attached is the graph of our kubenetes metrics for the pod. Note the constantly increasing cpu and that we lose jmx exporter (heap) metrics once the cpu becomes too high. Any help would be greatly appreciated. Best, Lavi-Feivel Blumberg Novus
