-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
revive reviveOffers #134
Labels
Comments
Note: discovered this issue while responding to #132 . |
Merged
@JessicaLHartog : I'm pretty sure this is obviated by the changes in PR #200 , so I'm going to assign this to you to move to its final disposition. |
Closing this per @JessicaLHartog 's comments. |
v0.2.4+ has this fix. For v0.1.x (storm-0.x support) we haven't done a release yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@brndnmtthws introduced the invocation of
_driver.reviveOffers()
to allow the framework to get previously declined offers sent back to itself.Then the call was was inadvertently removed by @dsKarthick in this refactoring change.
We should consider reintroducing it.
Note that
_reviveOffers()
is called every 10 seconds, since the frequency of the nimbus-core callingallSlotsAvailableForScheduling()
is driven by thenimbus.monitor.freq.secs
setting. This is pretty often, and much less than the default "filter seconds" of 120 seconds. I believe this means that with the default settings, we will never reach the 120 second timeout and the declined resources will be re-offered much more quickly.The text was updated successfully, but these errors were encountered: