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

maxvmem is reported incorrectly in qstat -j #36

Open
hoppo opened this issue Jul 6, 2024 · 0 comments
Open

maxvmem is reported incorrectly in qstat -j #36

hoppo opened this issue Jul 6, 2024 · 0 comments

Comments

@hoppo
Copy link

hoppo commented Jul 6, 2024

Hi,

I've noticed something curious about the reporting of memory - but perhaps I'm missed some configuration somewhere.
We previously used OGS/GE 2011.11p1 - and the behavior was not as we are seeing in this version (SGE r191.8.1.9-180-g657a9d1)

We use vmem as a limiting resource.
If a user consumes more vmem than they requested, their job is killed.
However, I have seen jobs which have been killed but report the maxvmem as much lower than what was requested (checked after the job died using qacct).

I have checked a running job using top, and it shows the following.

 PID    USER       PR  NI  VIRT    RES     SHR  S   %CPU  %MEM  TIME+   COMMAND                
 197143 xxxxxx     20   0  107.0g  11.3g   4.4g S   5.3   2.2   5:46.06 xxxxxxxxxx....... 

When I check this using using the qstat -j job_id command, I see the following:-

 usage         7:            cpu=00:05:04, mem=2570.35349 GB s, io=51.30660 GB, vmem=11.082G, maxvmem=11.108G

It would seem that qstat (and qacct) is misreporting res memory as vmem

OS - ubuntu 22.04

Any help or suggestions would be welcome.

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

No branches or pull requests

1 participant