Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

cgroup.memory.limit returning incorrect value? #85

Closed
hc000 opened this Issue Apr 14, 2016 · 2 comments

Comments

Projects
None yet
2 participants

hc000 commented Apr 14, 2016

While doing some testing I noticed this metric is returning the max value of 64-bit unsigned integer.

screen shot 2016-04-13 at 5 17 55 pm

Tested on a VM with 2GB of ram and a bare metal with 256GB of ram.
Saw this in Version 3.10.9-1 and 3.11.0

Contributor

natoscott commented Apr 14, 2016

Hi Henry,

This value is extracted directly the kernel via /sys/fs/cgroup/memory/[...]memory.limit_in_bytes ... do you see different values in those files?

hc000 commented Apr 14, 2016 edited

Hi Nathan,

It does indeed show match the value.

root@slave2:/sys/fs/cgroup/memory/docker/f4a901378ba4ef619091a4ee9c71607eeb81e25ec75bdd66184e147471d95dfe# cat memory.limit_in_bytes && cat memory.usage_in_bytes
18446744073709551615
29466624

Memory usage in bytes seems to be correct but not memory limit.

I think its related to this issue docker/docker#18087

Is there any metric that gets the values of MemTotal and MemFree from /proc/meminfo ?
MemTotal: 1017724 kB
MemFree: 660800 kB

these looks similar:

mem.physmem
value 1017724
mem.freemem
value 656860

@hc000 hc000 closed this Apr 14, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment