Skip to content
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

Closed
erikdw opened this issue Apr 22, 2016 · 5 comments
Closed

revive reviveOffers #134

erikdw opened this issue Apr 22, 2016 · 5 comments
Assignees

Comments

@erikdw
Copy link
Collaborator

erikdw commented Apr 22, 2016

@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 calling allSlotsAvailableForScheduling() is driven by the nimbus.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.

@erikdw
Copy link
Collaborator Author

erikdw commented Apr 22, 2016

Note: discovered this issue while responding to #132 .

@erikdw
Copy link
Collaborator Author

erikdw commented Aug 8, 2017

@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.

@JessicaLHartog
Copy link
Collaborator

You're right @erikdw, this is fixed in PR #200. Will close this issue once that's good to merge.

@erikdw
Copy link
Collaborator Author

erikdw commented Aug 16, 2017

Closing this per @JessicaLHartog 's comments.

@erikdw erikdw closed this as completed Aug 16, 2017
@erikdw
Copy link
Collaborator Author

erikdw commented Aug 16, 2017

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
Projects
None yet
Development

No branches or pull requests

2 participants