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
Stop jobs to pending if we dip below a threshold of free memory on a backend. Based on the most recent incident, my initial suggestion is 45GB free. We should try to use the same principle as db maintenance mode, i.e. reset to pending so that they automatically restart when resources become available (instead of erroring & requiring the end-user/researcher to re-run the job). My idea is that the most recently started job should be killed (i.e. FIFO).
Stop jobs to pending if we dip below a threshold of free memory on a backend. Based on the most recent incident, my initial suggestion is 45GB free. We should try to use the same principle as db maintenance mode, i.e. reset to pending so that they automatically restart when resources become available (instead of erroring & requiring the end-user/researcher to re-run the job). My idea is that the most recently started job should be killed (i.e. FIFO).
sibling ticket of #699
see discussion in slack thread
The text was updated successfully, but these errors were encountered: