Closed anoyli closed 3 years ago
@mxiamxia I remember you looked into the memory reading part.
The total memory seems to be 2^63 so definitely a bug somewhere.
Also another bug is that we display bytes not MB in the log, but that is an easy fix
@mxiamxia I remember you looked into the memory reading part.
The total memory seems to be 2^63 so definitely a bug somewhere.
Also another bug is that we display bytes not MB in the log, but that is an easy fix
Thank you @bogdandrutu , and i found whatever the machine memory i use, the total_memory is always 9223372036854771712
The issue has been fixed in https://github.com/open-telemetry/opentelemetry-collector/pull/3456. I think you will have the correct total memory when the new Collector release is out.
This is resolved now, we can close this. See #3456. cc @alolita
@anoyli can you give a try with 0.30.0 image?
@anoyli can you give a try with 0.30.0 image?
Great work, guys, thank you, i will take a try later and feedback if any result.
Closing issue since this request is resolved.
Describe the bug Hi Team, for the machine types vary much in our project, so we want to use percentage memory limiter to make it more reasonable to control the max memory usage of collector agent docker. However, we found the total number of machine memory not right. We use aws ec2 instance which have 30G memory, but when we check the log of collector agent, we found the memory number very huge, so it can't control the memory limit as our demand.
Steps to reproduce
What did you expect to see?
What did you see instead?
What version did you use?
What config did you use?
Environment
otel collector agent start logs