Thanks.
-Paul Edmon-
On 4/29/2013 10:34 AM, Carles Fenoy wrote:
Re: [slurm-dev] Re: JobHeldAdmin
Dear Paul,
You should be able to release the job with the command:
scontrol release JOBID
Regards,
Carles Fenoy
Barcelona Supercomputing Center
On Mon, Apr 29, 2013 at 3:49 PM, Carl Schmidtmann
<[email protected]
<mailto:[email protected]>> wrote:
Yes, changing the priority will release the hold. The priority
value you set will determine when it will attempt to run again. So
if you set the priority higher than other jobs it will run next.
If it is lower than other jobs it will wait.
Carl
------------------------------------------------------------------------
Okay, I did see a con/res error associated with these jobs.
So just to be clear modifying the job priority will clear the
Admin Hold state? I found that resubmitting the job also
works, but there is no way to do that besides removing the job
and having the user resubmit it.
-Paul Edmon-
On 4/29/2013 9:05 AM, Carles Fenoy wrote:
Hi,
This can happen if you are using gpu GRES with cpus
dedicated to some gpus. As Carl has said, check the
slurmctld log for any error.
Regards,
Carles Fenoy
Barcelona Supercomputing Center
On Mon, Apr 29, 2013 at 3:01 PM, Carl Schmidtmann
<[email protected]
<mailto:[email protected]>> wrote:
I am not sure of all the reasons a job might get to
the Admin Hold state but I have seen it when a job
tries to run but the resources it uses generate an
error instead of running the job. Once they are in
this state they will not be looked at by the scheduler
because the job has its priority set to zero. Changing
the priority to something greater than zero will put
them back into the scheduling. However, if the error
that caused them to fail still exists they will return
to the Admin Hold state when they next try to run.
Check the log files for the failure and possible reason.
Carl
----- Original Message -----
>
> What does this mean? I can't find any documentation
and I have
> several
> jobs in our queues which are getting this Reason
Waiting assigned
> them
> automatically by SLURM. The jobs themselves appear
valid, but I
> can't
> force them to lose this state even though there are
enough nodes for
> the
> job open.
>
> -Paul Edmon-
>
--
--
Carl Schmidtmann
Center for Integrated Research Computing
University of Rochester
- Our Annual CIRC Poster Session is May 10, 2013
- Visit
http://www.circ.rochester.edu/poster_submission.html
--
--
Carles Fenoy
--
--
Carl Schmidtmann
Center for Integrated Research Computing
University of Rochester
- Our Annual CIRC Poster Session is May 10, 2013
- Visithttp://www.circ.rochester.edu/poster_submission.html
--
--
Carles Fenoy
