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

Setting hard memory limit constraints fails on certain systems #123

Open
EricR86 opened this issue Jan 30, 2018 · 0 comments
Open

Setting hard memory limit constraints fails on certain systems #123

EricR86 opened this issue Jan 30, 2018 · 0 comments
Labels
bug Something isn't working major

Comments

@EricR86
Copy link
Member

EricR86 commented Jan 30, 2018

Original report (BitBucket issue) by Eric Roberts (Bitbucket: ericr86, GitHub: ericr86).


On job resubmission, segway-wrapper.sh attempts to raise both the hard and soft limits of virtual and resident set size memory.

If the hard limit of memory is not unlimited, only root users may increase the hard memory limit requested even after it has been lowered.

Perhaps a proprosal to fallback to attempting to change only the soft limit after failing to set both hard and soft limit.

e.g:

#!bash

ulimit -c 0 -v "$mem_limit_kb" -m "$mem_limit_kb" || (
ulimit -S -c 0 -v "$mem_limit_kb" -m "$mem_limit_kb" || exit 201)
@EricR86 EricR86 added major bug Something isn't working labels Apr 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working major
Projects
None yet
Development

No branches or pull requests

1 participant