Hi Carles, Thanks for your reply. I dont see any error in the logs files. I use -v flag and there arent errors. Thanks for your explain about backfillI used backfilling because it was the default option, but I had to eliminate the walltime limits due to some user complaints. This strange behaviour only affect a one specific user. He can send several jobs to the queue (and are dispatched and work fine), but seems like there was "a limit in the number of running jobs or resources for this user", after that, his works arent dispatched (dont appear) but the other works are running, also he can submit other jobs using less resources. Although there are enough free resources. Thanks in advance. Regards.
Date: Wed, 7 Aug 2013 01:13:44 -0700 From: [email protected] To: [email protected] Subject: [slurm-dev] Re: Jobs not queued in SLURM 2.3 Re: [slurm-dev] Jobs not queued in SLURM 2.3 Hi José Manuel, Do you see any error on the controller logfile? Having backfilling with ulimited time jobs is useless because it will never backfill a job, but should not affect on the "non appearing" jobs issue. Are any of the user jobs dispatched? Regards, Carles Fenoy Barcelona Supercomputing Center On Wed, Aug 7, 2013 at 9:57 AM, José Manuel Molero <[email protected]> wrote: Hi, I have a cluster working fine with Slurm 2.3 But I noticed that a specific user can not queue (or dispatch) many works at the same time.When this user queue many jobs, the following jobs are submitted correctly (give a job number) but not added to the queue. And the cluster have free resources. https://computing.llnl.gov/linux/slurm/faq.html#time This is not the problem, because other user can allocate jobs without problems. The scheduler type si backfill, and all the jobs are time unlimited. Could this be the problem?Why the jobs dissapear (not added to the queue) and not passed to PD state if there are free resources? Thanks in advance. Best regards. -- -- Carles Fenoy
