Closed jeremyaouad closed 1 year ago
Pinging code owners: @djaglowski. See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been closed as inactive because it has been stale for 120 days with no activity.
Description
I have code emitting metrics and logs to a collector. The collector then emits to a visualizer. I'm doing a test where I
kill -STOP
the visualizer for 10 minutes, and switch it back on, in order to test the compaction on rebound. Only after the visualizer comes back online, I expect to have compaction, and not before. I configured compaction as follows:Since bbolt mmaps disk to memory, I am monitoring the memory of the collector process and cpu.
Actual Result
Compaction on rebound:
Same scenario without compaction: We can see that memory goes up above 4 GB after the collector resumes sending to the continued visualizers. This is where I expected to see compaction on rebound happening.
Collector version
0.54.0
Environment information
Environment
OS: Red Hat Enterprise Linux release 8.5 (Ootpa) Compiled on: rhel8 - gcc8 cpp17
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response