planner: simplify accounting during migration #427
Merged
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.
There was a bug in the accounting logic during a DIST_CHANGE request. At this point, we need to release the slots of the to-be migrated function, and claim them in the migrated-to hosts.
The current logic assumed that, given two decisions, they would always start being similar, and then diverge (or even diverge all the way through).
This is not the case. Take for example the following situation where A has 5 slots:
Using our accounting logic, for a while we would have 7 slots assigned to A. This would break our assertions (did not catch it because it only happens in Release builds), but was breaking the MPI port assignation.