You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was brought up in our team meeting yesterday that eventually, the plugin should be able to support bypassing limits for certain users' jobs. This could be handled (at least at first) by unpacking and checking for a certain attribute in the callbacks that increase/decrease limits.
For example, in job.new, if we find this attribute, we can skip this increment of the users' active_jobs count:
This was brought up in our team meeting yesterday that eventually, the plugin should be able to support bypassing limits for certain users' jobs. This could be handled (at least at first) by unpacking and checking for a certain attribute in the callbacks that increase/decrease limits.
For example, in
job.new
, if we find this attribute, we can skip this increment of the users'active_jobs
count:flux-accounting/src/plugins/mf_priority.cpp
Line 827 in b291ffb
Or ignore a user's
running_jobs
count by skipping the increment in the callback forjob.state.run
:flux-accounting/src/plugins/mf_priority.cpp
Line 908 in b291ffb
The text was updated successfully, but these errors were encountered: