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

Wrong RAM consumtion on poststart sidecar tasks #24758

Open
iGorebach opened this issue Dec 26, 2024 · 1 comment
Open

Wrong RAM consumtion on poststart sidecar tasks #24758

iGorebach opened this issue Dec 26, 2024 · 1 comment
Labels

Comments

@iGorebach
Copy link

Nomad version

1.8.3

Operating system and Environment details

Ubuntu 22.04, kernel version 6.5.0-35-generic

Issue

Wrong memory utilization is displayed in UI and in Nomad metrics for the post-start sidecar tasks, which work with the filesystem.

Total job memory usage
image
Poststart sidecar task memory usage
image
Real memory usage

docker stats a9481fb2f57d --no-stream
CONTAINER ID   NAME                                          CPU %     MEM USAGE / LIMIT   MEM %     NET I/O   BLOCK I/O    PIDS
a9481fb2f57d   backup-9d2f286d-a117-d31a-0e41-67c997fe08d4   0.00%     15.22MiB / 1GiB     1.49%     0B / 0B   0B / 952MB   4

similar issue

Reproduction steps

Create the poststart sidecar container, working in cmd loop with fs write operations or connect to task manually and create a file on /alloc mount point.

Expected Result

No memory consumption affected

Actual Result

Every file created increases RAM utilization by its size, real utilization is different.

@iGorebach
Copy link
Author

The same behavior occurred when CSI volumes were used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant