On Thu, May 14, 2015 at 4:31 PM, Reuti <[email protected]> wrote:
> Am 14.05.2015 um 20:22 schrieb Michael Stauffer: > > > OGS, via Rocks 6.1 > > > > Hi, > > > > Sometimes users have jobs running that fill they're quota, and want to > suspend one of them in order to run a different immediate job, and then > continue the suspended job. I've experimented with suspending running jobs > and submitting a new job, but the new job doesn't run. Should it? Is there > a different way to do this? > > How should SGE know which job to suspend to lower the quota temporarily? > There is no look-ahead feature in SGE to make such decisions. Once resource > are granted, they are used up also by suspended jobs. > I was experimenting with suspending the jobs manually, so SGE wouldn't have to decide. But in any case, seems my goal isn't possible using suspension, thanks, so I'll stick with placing holds on queued jobs, and look into checkpointing. -M > -- Reuti > > > > Related to this, I've seen that if the user's quota is full and also has > a number of queued jobs, the queued jobs can have a hold placed on them, > and a newly submitted job will then run once one of the running jobs has > completed. This works for some cases, but if the running jobs are long, > it's less attractive. > > > > Thanks > > > > -M > > _______________________________________________ > > users mailing list > > [email protected] > > https://gridengine.org/mailman/listinfo/users > >
_______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
