Return resource control to ats to avoid scheduling issues with the flux adapter. #107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Had found in testing that the split in resource tracking across ats/flux was confusing the schedulers a bit, resulting in much lower than expected throughput when dealing with lots of short lived jobs.
Additionally, the scheduled time limit on the flux mini run was disabled to return control of that to ats's scheduling: flux was refusing to schedule jobs when too close to the end time, but ats wasn't able to pick up on that and just idled resources.
This MR addresses the issues mentioned in #106.