hi we have situations where users would like to submit thousands of jobs and forget about it and just leave it to the scheduler to figure things out. we also have TRES enabled for qos which ensures that no users occupies more than 1/3 of the resources.
however, backfilling appears to go through all jobs of a given user even when bf_max_job_user is set to something like 50. i would have expected the backfill scheduler to: 1. sort by priority 2. ignore any jobs for users already at TRES@qos limit for remaining jobs: 3. loop through jobs, backfilling as necessary a. but only up to *bf_max_job_user* number of jobs per user. b. if one has already seen *bf_max_job_user* jobs from that user, ignore any more jobs during the current round of backfill this would be very helpful in our scenario. cheers, satra
