Skip to content

Account for expected usage when scoring offers #1720

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

Merged
merged 8 commits into from
Feb 26, 2018
Merged

Conversation

ssalinas
Copy link
Member

Right now it's possible for us to easily overload a fairly empty machine if we have lots of tasks to schedule. The way the score is calculated, we don't account for other tasks we may have just scheduled. This adds the reserved and last recorded max usage to factoring into scoring, updating those after each task is added to an offer host.

@ssalinas ssalinas added this to the 0.20.0 milestone Feb 20, 2018
@ssalinas ssalinas added the hs_qa label Feb 21, 2018
case LOAD_5:
default:
return slaveUsage.getSystemLoad15Min();
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Fat-finger switcheroo here

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks, fixed

@baconmania
Copy link
Contributor

🚢

@ssalinas ssalinas merged commit 09f7982 into master Feb 26, 2018
@ssalinas ssalinas deleted the expected_usage branch February 26, 2018 16:55
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.

2 participants