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
I have encountered a couple of situations in testing where the preallocator's machines datastructure got out of sync. There were machine ids in the list that no longer had an entry in the relevant queue, which prevented any jobs from being scheduled on that machine. If all machines get in that state, job scheduling would halt. #77 fixes some of these, but it probably makes sense to either reset the preallocator state or validate it when tango is reset.
The text was updated successfully, but these errors were encountered:
I have encountered a couple of situations in testing where the preallocator's machines datastructure got out of sync. There were machine ids in the list that no longer had an entry in the relevant queue, which prevented any jobs from being scheduled on that machine. If all machines get in that state, job scheduling would halt. #77 fixes some of these, but it probably makes sense to either reset the preallocator state or validate it when tango is reset.
The text was updated successfully, but these errors were encountered: