Dear SLURM,

If I am a regular user and imagine I have ton's of jobs submitted, then I come 
up with another batch of jobs that I want to run before that batch I submitted 
few hours back that is still in the queue waiting for resources and priority. 
Is there a way to do this?  From an admin perspective I wouldn't want this, 
because users could misuse this feature. But from a user perspective I could 
genuinely have some dependencies that I would like to have it addressed before 
beginning my batch of thousands of jobs.

Any help here is greatly appreciated.

Regards,
Amit

Reply via email to