Hi guys, Thanks for the replay. I will try to add my slurm.conf tomorrow. Sadly, its a bit of a problem since its on a cluster disconected from the net and with no easy way of getting it out :(
I will try tomorrow with the hope that any body could catch some bad parameter. Thanks, Roy On Nov 13, 2017 7:38 PM, "Douglas Jacobsen" <dmjacob...@lbl.gov> wrote: Assuming you are using backfill, I suspect this is caused by using default schedulerparameters, specifically the bf maxjobs or other similar limits that would prevent jobs from being reviewed. Setting debugflags=backfill will help greatly in debugging these issues. There are analogous parameters for the lightweight, non backfill scheduler. Checking slurm.conf man page under schedulerparameters should be very informative. On Nov 13, 2017 10:29, "A" <andrealp...@gmail.com> wrote: > I'm guessing you should have sent them to cluster Decepticon, instead.... > > In all seriousness though, provide the conf file. You might have > accidentally set a maximum number of running jobs somewhere > > > On Nov 13, 2017 7:28 AM, "Benjamin Redling" <benjamin.ra...@uni-jena.de> > wrote: > >> Hi Roy, >> >> On 11/13/17 2:37 PM, Roe Zohar wrote: >> [...] >> >>> I sent 3000 jobs with feature Optimus and part are running while part >>> are pendind. Which is ok. >>> But I have sent 1000 jobs to Megatron and they are all in pending >>> stating they wait because of priority. Whay os that? >>> >>> B.t.w if I change their priority to a higher one, they start to run on >>> Megatron. >>> >> >> my guess: is if you can provide the slurm.conf of that cluster, the >> probability anyone will sacrifice his spare-time for you will increase >> significantly. >> >> Regards, >> Benjamin >> -- >> FSU Jena | JULIELab.de/Staff/Benjamin+Redling.html >> ☎ +49 3641 9 44323 >> >>
