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

Support global overrides of request placement strategy/rack sensitivity #2228

Merged
merged 2 commits into from
Sep 17, 2021

Conversation

WH77
Copy link
Contributor

@WH77 WH77 commented Aug 26, 2021

This PR exists to speed up response/recovery time in the event of a rack outage, via new API endpoints that will set global configuration overrides of request placement strategy and/or rack sensitivity on the current leader.

@@ -56,6 +56,7 @@ public void runActionOnPoll() {
lock.runWithRequestLock(
() -> {
SingularityRequest request = requestWithState.getRequest();
// TODO - support global override here?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can probably ignore for this spread all case, it should just continue to try and scale to whatever remains

Copy link
Member

@ssalinas ssalinas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two overall comments:

  • not sure if this belongs in the RackResource or not? I'm wondering if we need a new/separate AdminConfigurationResource or something like that? There is also the DisastersResource that has a hodge-podge of emergency action endpoints
  • should the endpoint just allow us to globally set the PlacementStrategy, vs defaulting everything to OPTIMISTIC based on a boolean? Wondering if we'd ever need GREEDY vs OPTIMISTIC

@pschoenfelder
Copy link
Contributor

🚢

@WH77 WH77 merged commit d9443e8 into master Sep 17, 2021
@WH77 WH77 deleted the live-configuration branch September 17, 2021 18:19
@ssalinas ssalinas added this to the 1.5.0 milestone May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants