Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nomad_1.3.0-beta.1 - memory stats shows 0 with cgroupv2 #12931

Closed
Oleksii-Melnyk-UA opened this issue May 10, 2022 · 3 comments
Closed

nomad_1.3.0-beta.1 - memory stats shows 0 with cgroupv2 #12931

Oleksii-Melnyk-UA opened this issue May 10, 2022 · 3 comments
Labels

Comments

@Oleksii-Melnyk-UA
Copy link

Nomad version

nomad_1.3.0-beta.1

Operating system and Environment details

Flatcar 3033.2.2
https://www.flatcar.org/releases/#release-3033.2.2

Issue

I used previously Flatcar version 2765.2.1 and nomad 1.0.4. At that time I could see memory metric for containers provided by Nomad.
But after update to Flatcar 3033.2.2, memory metric always shows 0.
I assumed that the reason is that new Flatcar version become using cgroupsv2.
Found similar issue - #10251

So, I updated Nomad version to 1.3.0-beta.1 .
But with 1.3.0-beta.1 memory metric still shows 0.

Can you, please, help to fix this issue.

@shoenig
Copy link
Member

shoenig commented May 10, 2022

@Oleksii-Melnyk-UA thanks for experimenting with the Nomad 1.3 beta.

Are you able to reproduce the problem using the rc.1 release?
https://releases.hashicorp.com/nomad/1.3.0-rc.1

memory metric always shows 0

What specifically are you looking at that you expect to be non-zero?

What task driver are you using? Can you share a minimal job file that reproduces the problem?

@Oleksii-Melnyk-UA
Copy link
Author

Found that see memory metric on 1.3.0-rc.1 nomad release using command:
nomad status job_name
nomad alloc-status alloc-id

@github-actions
Copy link

github-actions bot commented Oct 8, 2022

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
Development

No branches or pull requests

2 participants