-
Notifications
You must be signed in to change notification settings - Fork 123
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
missing slurm qos parameter #300
Comments
There is no such
|
Thanks. It would be helpful to me if this could be added as an option. I
may have jobs running in different accounts and partitions at the same
time. They could also get stuck in the queue and then I would not be sure
which value it would run with if I am changing the configuration file
between submissions. Or even what value any jobs spawned later would get.
This isn't purely theoretical I was actually trying to do this recently.
The account is required with the qos parameter.
Belinda
…On Mon, 6 Nov 2023, Jin wook Lee wrote:
There is no such `slurm-qos` parameter in Caper. But you can still customize the leader job submission command line in Caper's conf file (`~/.caper/default.conf`) here. Also please remove `slurm-account` if it's not required for your cluster.
```
slurm-partition=burst
#slurm-account=xxxxxx <------ please remove this if not needed
...
slurm-leader-job-resource-param=-t 48:00:00 --mem 4G DEFINE_ANY_EXTRA_QOS_PARAMETER_HERE
```
--
Reply to this email directly or view it on GitHub:
#300 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First I am able to run the pipeline in the open queue, so I know that everything is installed properly. In case it makes a difference, this is a conda install, with Slurm. But I would like to be able to run this under an allocation to avoid long queues. In our system we need to not only define the account and partition but also the qos. This fails with the ENCODE pipelines. In the slurm*.out files I see that the qos is not being used.
In default.conf:
slurm-partition=burst
slurm-qos=burst3x
In slurm*.out:
2023-10-13 12:37:15,399|caper.hpc|INFO| Running shell command: sbatch -t 48:00:00 --mem 4G -p burst -A xxxx --export=ALL -J CAPER_62 /storage/home/bmg137/miaq8ut7.sh
sbatch: error: Batch job submission failed: Invalid qos specification
Belinda
The text was updated successfully, but these errors were encountered: