[
https://issues.apache.org/jira/browse/ARTEMIS-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Månsson updated ARTEMIS-4422:
------------------------------------
Environment:
EKS bottlerocket containerd EC2 nodes.
amazoncorretto:17 image (Java 17 JRE)
Artemis 2.30.0
2 node cluster, with one node having producers and consumers and the other
acting as fail over
persistance disabled
was:
EKS bottlerocket containerd EC2 nodes.
amazoncorretto:17 image (Java 17 JRE)
Artemis 2.30.0
> High container memory usage per address size
> --------------------------------------------
>
> Key: ARTEMIS-4422
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4422
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.30.0
> Environment: EKS bottlerocket containerd EC2 nodes.
> amazoncorretto:17 image (Java 17 JRE)
> Artemis 2.30.0
> 2 node cluster, with one node having producers and consumers and the other
> acting as fail over
> persistance disabled
> Reporter: Tobias Månsson
> Priority: Major
>
> We are running a 2 instance clustered Artemis setup, were just one instance
> has producers and consumers and the other is a fail over. It's running on EKS
> bottlerocket nodes (containerd runtime), in a Java 17 JRE environment.
> We've had issues with high memory usage for our Artemis broker for a long
> time, but yesterday several events raised a possible candidate to the cause.
> We had sudden drops in address size correlating to container memory drops,
> and calculations show that each "address size" byte takes 40- 160 "container"
> bytes.
> Is this normal and intended?
> Should the parameter max-size-bytes be multiplied by say 100 to get
> "actually" container memory usage?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
