Hi, on 15.08.5 we have a config where students are only allowed a maximum of 10 cores by using GrpTRES / cpu=10. We also have activated fairshare (using FAIR_TREE).
Now when student 1 submits jobs beyond his limits of 10 cores, they are correctly put into state "pending" (showing AssocGrpCpuLimit). So far so good. The problem arises when another non-student user 1 with much lower fairshare priority value submits a job: That user's job doesn't start even though there are free resources. It is sitting in the queue because it's overall priority is lower than the student's pending job. Is this expected behavior or shouldn't the job of user 1 start regardless of lower priority, since student 1's job can't start anyway because of the 10 core limit? This problem essentially blocks the cluster as soon as students submit beyond their limit. Thanks, Roland ------- http://www.q-leap.com / http://qlustar.com --- HPC / Storage / Cloud Linux Cluster OS ---
