Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Observation

When you are observing high heap and memory consumption and it grows rapidly over a number of days to its max value. As soon as it reaches the max value, the Hivemq service gets restarted

Explanation

s3Client was not closed correctly in HiveMQS3Client, which resulted memory leak.
This is a known issue and addressed in the S3 Cluster Discovery Extension 4.1.1

Affected versions

This affects HiveMQ S3 Cluster Discovery Extension 4.1.0 version.
A fix is included in S3 Cluster Discovery Extension 4.1.1

  • No labels